Thanks SmileyChris for the patch.

Tests were still failing with MySQL. It seems a rollback is solving
the issue.

Thanks to milosu for the report, tests and initial patch.

Thanks Eli Collins for the report and the patch.

Applied the rule that string encoding should happen as late as
possible. This is also a preparation for Python 3 compatibility.

Thanks Will Hardy for the report and the patch.

This is a good practice for accessibility.
Thanks Jessica McKellar for the report.

When constructing a polygon with Polygon.from_bbox, do not convert
parameters to strings at this stage (str defaults to 12 significant
digits).
Thanks tdihp@hotmail.com for the report and David Eklung for the patch.

Thanks msiedlarek, jpaugh64 and vlinhart!

Django Admin's input for BigIntegerField should be larger, Fixes #17804 

Both false positives and false negatives of HttpRequest.is_secure can be
dangerous.

Docs: "Form in a view" example doesn't use RequestContext

Fixed #17138 -- Removed the 'summary' attribute from the admin index tables to be html5-valid.

In previous version it used /django/forms/ which was fragile - for some
users .pyc files were not generated and this tests failed.

In the discussion here: https://code.djangoproject.com/ticket/17138
it was decided that using the caption for this previously
non-visible part of the table element was not semantic, so in this
patch is moves that summary to the `title` attribute of the `a`
tag which when overed over, on most browsers, will show the text.

self.settings_override from test subclasses were overwriting parent
attribute.

When using the template system in standalone mode and if the url
template tag is used, ROOT_URLCONF has to be defined.
Thanks techtonik for the report.

Implemented this by adding a stealth table_name_filter option for the
command.

Fixed #18409 -- Made RegexField work with unicode characters.

Resolves Flatpages test issues by:
 - Creating an example_site fixture
 - Overriding project SITE_ID setting to 1
 - Normalizing the use of the hardcoded (1) site_id to settings.SITE_ID

When generating error message in to_python, any unicode string
containing non-ascii characters triggered a UnicodeEncodeError for
most field types.