251 lines
4.6 KiB
Plaintext
251 lines
4.6 KiB
Plaintext
=============================================
|
|
Django 1.11 release notes - UNDER DEVELOPMENT
|
|
=============================================
|
|
|
|
Welcome to Django 1.11!
|
|
|
|
These release notes cover the `new features`_, as well as some `backwards
|
|
incompatible changes`_ you'll want to be aware of when upgrading from Django
|
|
1.10 or older versions. We've `begun the deprecation process for some
|
|
features`_.
|
|
|
|
.. _`new features`: `What's new in Django 1.11`_
|
|
.. _`backwards incompatible changes`: `Backwards incompatible changes in 1.11`_
|
|
.. _`begun the deprecation process for some features`: `Features deprecated in 1.11`_
|
|
|
|
Django 1.11 is designated as a :term:`long-term support release`. It will
|
|
receive security updates for at least three years after its release. Support
|
|
for the previous LTS, Django 1.8, will end 6 months after the release date of
|
|
Django 1.11.
|
|
|
|
Python compatibility
|
|
====================
|
|
|
|
Like Django 1.10, Django 1.11 requires Python 2.7, 3.4, or 3.5. We **highly
|
|
recommend** and only officially support the latest release of each series.
|
|
|
|
The Django 1.11.x series is the last to support Python 2. The next major
|
|
release, Django 2.0, will only support Python 3.5+.
|
|
|
|
Deprecating warnings are no longer loud by default
|
|
==================================================
|
|
|
|
Unlike older versions of Django, Django's own deprecation warnings are no
|
|
longer displayed by default. This is consistent with Python's default behavior.
|
|
|
|
This change allows third-party apps to support both Django 1.11 LTS and Django
|
|
1.8 LTS without having to add code to avoid deprecation warnings.
|
|
|
|
Following the release of Django 2.0, we suggest that third-party app authors
|
|
drop support for all versions of Django prior to 1.11. At that time, you should
|
|
be able run your package's tests using ``python -Wd`` so that deprecation
|
|
warnings do appear. After making the deprecation warning fixes, your app should
|
|
be compatible with Django 2.0.
|
|
|
|
What's new in Django 1.11
|
|
=========================
|
|
|
|
Minor features
|
|
--------------
|
|
|
|
:mod:`django.contrib.admin`
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
* ...
|
|
|
|
:mod:`django.contrib.admindocs`
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
* ...
|
|
|
|
:mod:`django.contrib.auth`
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
* The default iteration count for the PBKDF2 password hasher is increased by
|
|
20%.
|
|
|
|
:mod:`django.contrib.contenttypes`
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
* ...
|
|
|
|
:mod:`django.contrib.gis`
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
* ...
|
|
|
|
:mod:`django.contrib.messages`
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
* ...
|
|
|
|
:mod:`django.contrib.postgres`
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
* ...
|
|
|
|
:mod:`django.contrib.redirects`
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
* ...
|
|
|
|
:mod:`django.contrib.sessions`
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
* ...
|
|
|
|
:mod:`django.contrib.sitemaps`
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
* ...
|
|
|
|
:mod:`django.contrib.sites`
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
* ...
|
|
|
|
:mod:`django.contrib.staticfiles`
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
* ...
|
|
|
|
:mod:`django.contrib.syndication`
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
* ...
|
|
|
|
Cache
|
|
~~~~~
|
|
|
|
* ...
|
|
|
|
CSRF
|
|
~~~~
|
|
|
|
* ...
|
|
|
|
Database backends
|
|
~~~~~~~~~~~~~~~~~
|
|
|
|
* ...
|
|
|
|
Email
|
|
~~~~~
|
|
|
|
* ...
|
|
|
|
File Storage
|
|
~~~~~~~~~~~~
|
|
|
|
* To make it wrappable by :class:`io.TextIOWrapper`,
|
|
:class:`~django.core.files.File` now has the ``readable()``, ``writable()``,
|
|
and ``seekable()`` methods.
|
|
|
|
File Uploads
|
|
~~~~~~~~~~~~
|
|
|
|
* ...
|
|
|
|
Forms
|
|
~~~~~
|
|
|
|
* ...
|
|
|
|
Generic Views
|
|
~~~~~~~~~~~~~
|
|
|
|
* ...
|
|
|
|
Internationalization
|
|
~~~~~~~~~~~~~~~~~~~~
|
|
|
|
* ...
|
|
|
|
Management Commands
|
|
~~~~~~~~~~~~~~~~~~~
|
|
|
|
* ...
|
|
|
|
Migrations
|
|
~~~~~~~~~~
|
|
|
|
* ...
|
|
|
|
Models
|
|
~~~~~~
|
|
|
|
* ...
|
|
|
|
Requests and Responses
|
|
~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
* ...
|
|
|
|
Serialization
|
|
~~~~~~~~~~~~~
|
|
|
|
* ...
|
|
|
|
Signals
|
|
~~~~~~~
|
|
|
|
* ...
|
|
|
|
Templates
|
|
~~~~~~~~~
|
|
|
|
* ...
|
|
|
|
Tests
|
|
~~~~~
|
|
|
|
* ...
|
|
|
|
URLs
|
|
~~~~
|
|
|
|
* ...
|
|
|
|
Validators
|
|
~~~~~~~~~~
|
|
|
|
* ...
|
|
|
|
Backwards incompatible changes in 1.11
|
|
======================================
|
|
|
|
Database backend API
|
|
--------------------
|
|
|
|
* ...
|
|
|
|
Dropped support for PostgreSQL 9.2 and PostGIS 2.0
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
Upstream support for PostgreSQL 9.2 ends in September 2017. As a consequence,
|
|
Django 1.11 sets PostgreSQL 9.3 as the minimum version it officially supports.
|
|
|
|
Support for PostGIS 2.0 is also removed as PostgreSQL 9.2 is the last version
|
|
to support it.
|
|
|
|
Miscellaneous
|
|
-------------
|
|
|
|
* If no items in the feed have a ``pubdate`` or ``updateddate`` attribute,
|
|
:meth:`SyndicationFeed.latest_post_date()
|
|
<django.utils.feedgenerator.SyndicationFeed.latest_post_date>` now returns
|
|
the current UTC date/time, instead of a datetime without any timezone
|
|
information.
|
|
|
|
* Support for SpatiaLite < 4.0 is dropped.
|
|
|
|
.. _deprecated-features-1.11:
|
|
|
|
Features deprecated in 1.11
|
|
===========================
|
|
|
|
Miscellaneous
|
|
-------------
|
|
|
|
* ...
|