Django 1.8.3 版本发行说明

    Django 1.8.3 fixes several security issues and bugs in 1.8.2.

    Also, was renamed to RemovedInDjango110Warning as the version roadmap was revised to 1.9, 1.10, 1.11 (LTS), 2.0 (drops Python 2 support). For backwards compatibility, RemovedInDjango20Warning remains as an importable alias.

    The built-in session backends now create a session record only if the session is actually modified; empty session records are not created. Thus this potential DoS is now only possible if the site chooses to expose a session-modifying view to anonymous users.

    As each built-in session backend was fixed separately (rather than a fix in the core sessions framework), maintainers of third-party session backends should check whether the same vulnerability is present in their backend and correct it if so.

    validate_ipv4_address(), , and URLValidator are also affected, however, as of Django 1.6 the GenericIPAddresseField, IPAddressField, SlugField, and URLField form fields which use these validators all strip the input, so the possibility of newlines entering your data only exists if you are using these validators outside of the form fields.

    The undocumented, internally unused validate_integer() function is now stricter as it validates using a regular expression instead of simply casting the value using int() and checking if an exception was raised.

    • Fixed BaseRangeField.prepare_value() to use each base_field’s prepare_value() method ().
    • Fixed crash during makemigrations if a migrations module either is missing __init__.py or is a file ().
    • Fixed returning incorrect results after annotation with Count() (#24835).
    • Corrected HStoreField.has_changed() ().
    • Reverted an optimization to the CSRF template context processor which caused a regression (#24836).
    • Fixed a regression which caused template context processors to overwrite variables set on a RequestContext after it’s created ().
    • Fixed a crash when using a reverse one-to-one relation in ModelAdmin.list_display (#24851).
    • Fixed quoting of SQL when renaming a field to AutoField in PostgreSQL ().
    • Fixed lack of unique constraint when changing a field from primary_key=True to unique=True (#24893).
    • Fixed queryset pickling when using prefetch_related() after deleting objects ().
    • Allowed using choices longer than 1 day with DurationField (#24897).
    • Fixed a crash when loading squashed migrations from two apps with a dependency between them, where the dependent app’s replaced migrations are partially applied ().
    • Fixed recording of applied status for squashed (replacement) migrations (#24628).
    • Fixed queryset annotations when using Case expressions with exclude() ().
    • Corrected join promotion for multiple Case expressions. Annotating a query with multiple expressions could unexpectedly filter out results (#24924).
    • Fixed usage of transforms in subqueries ().
    • Provided better backwards compatibility for the verbosity argument in optparse management commands by casting it to an integer (#24769).
    • Fixed prefetch_related() on databases other than PostgreSQL for models using UUID primary keys ().
    • Fixed removing unique_together constraints on MySQL (#24972).
    • Fixed crash when uploading images with MIME types that Pillow doesn’t detect, such as bitmap, in forms.ImageField ().
    • Fixed a regression when deleting a model through the admin that has a GenericRelation with a related_query_name (#24940).
    • Reallowed non-ASCII values for ForeignKey.related_name on Python 3 by fixing the false positive system check ().
    • Fixed inline forms that use a parent object that has a UUIDField primary key and a child object that has an AutoField primary key (#24958).
    • Fixed a regression in the unordered_list template filter on certain inputs ().
    • Fixed a regression in URLValidator that invalidated Punycode TLDs (#25059).
    • Improved pyinotify runserver polling ().