Document password truncation with BCryptPasswordHasher
Merge pull request #962 from dstufft/document-bcrypt-truncation-1.4.x

Document password truncation with BCryptPasswordHasher
[1.4.x] Bump version to no longer claim to be 1.4.5 final.
[1.4.x] Fixed #20150 -- Fixed an error in manager doc example

Backport of 485c024567 from master
[1.4.X] Fixed #18277 - Clarified startproject documentation.

Backport of 33503600b5 from master
[1.5.X] Fixed #18883 -- added a missing self parameter in the docs

Backport of 17d57275f9 from master
[1.4.x] Fixed a minor spelling mistake in the queryset documentation

Backport of d258cce482 from master
[1.4.x] Updated link to jQuery Cookie plugin site

Backport of 81f454a322 from master
[1.5.x] Fixed #20492 - Removed a broken link in GIS docs.

Backport of fbab3209fc from master
[1.4.x] Fixed #20523 - Incorrect form field for FilePathField.

Thanks sane4ka.sh@ for the report.

Backport of 1fdc3d256d from master
[1.4.x] Fixed regroup example.

Chicago was missing.

Backport of e6ff238 from master.
[1.4.x] Fixed #20326 - Corrected form wizard get_form() example.

Thanks tris@ for the report.

Backport of 646a2216e9 from master
[1.4.x] Fixed #20636 -- Stopped stuffing values in the settings.

In Django < 1.6, override_settings restores the settings module that was
active when the override_settings call was executed, not when it was
run. This can make a difference when override_settings is applied to a
class, since it's executed when the module is imported, not when the
test case is run.

In addition, if the settings module for tests is stored alongside the
tests themselves, importing the settings module can trigger an import
of the tests. Since the settings module isn't fully imported yet,
class-level override_settings statements may store a reference to an
incorrect settings module. Eventually this will result in a crash during
test teardown because the settings module restored by override_settings
won't the one that was active during test setup.

While Django should prevent this situation in the future by failing
loudly in such dubious import sequences, that change won't be backported
to 1.5 and 1.4. However, these versions received the "allowed hosts"
patch and they're prone to "AttributeError: 'Settings' object has no
attribute '_original_allowed_hosts'". To mitigate this regression, this
commits stuffs _original_allowed_hosts on a random module instead of the
settings module.

This problem shouldn't occur in Django 1.6, see #20290, but this patch
will be forward-ported for extra safety.

Also tweaked backup variable names for consistency.

Backport of 0261922 from stable/1.5.x.

Conflicts:
	django/test/utils.py
[1.4.x] Fixed oversight in e3b6fed3. Refs #20636.
[1.4.x] Fixed #20665 -- Missing backslash in sitemaps documentation

Backport of 5005303ae7919eef26dab9f8ba279696966ebf1d from master.
[1.4.x] Fixed #18944 -- Documented PasswordResetForm's from_email argument as a backwards incompatible change for 1.3

Thanks DrMeers for the report.

Backport of dab921751d from master
[1.4.x] Fixed #19196 -- Added test/requirements

Backport of 4d92a0bd86 from master
[1.4.x] Fixed #20730 -- Fixed "Programmatically creating permissions" error.

Thanks glarrain for the report.

Backport of 684a606a4e from master
[1.4.x] Fixed #20756 -- Typo in uWSGI docs.

Backport of a3242dc9fe from master
[1.4.x] Atom specification URL updated

Changed to the URL of the official RFC for Atom, since Atomenabled.org
is just a holding page.

Backport of beefc97171 from master