123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265 |
- ============================================
- Django 2.0 release notes - UNDER DEVELOPMENT
- ============================================
- Welcome to Django 2.0!
- These release notes cover the :ref:`new features <whats-new-2.0>`, as well as
- some :ref:`backwards incompatible changes <backwards-incompatible-2.0>` you'll
- want to be aware of when upgrading from Django 1.11 or earlier. We've
- :ref:`dropped some features<removed-features-2.0>` that have reached the end of
- their deprecation cycle, and we've :ref:`begun the deprecation process for some
- features <deprecated-features-2.0>`.
- See the :doc:`/howto/upgrade-version` guide if you're updating an existing
- project.
- Python compatibility
- ====================
- Django 2.0 supports Python 3.5+. Since Django 1.11, support for Python 2.7 and
- 3.4 is removed. We **highly recommend** and only officially support the latest
- release of each series.
- Third-party library support for older version of Django
- =======================================================
- 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.
- .. _whats-new-2.0:
- What's new in Django 2.0
- ========================
- Minor features
- --------------
- :mod:`django.contrib.admin`
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~
- * ...
- :mod:`django.contrib.admindocs`
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- * ...
- :mod:`django.contrib.auth`
- ~~~~~~~~~~~~~~~~~~~~~~~~~~
- * ...
- :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
- ~~~~~~~~~~~~
- * ...
- File Uploads
- ~~~~~~~~~~~~
- * ...
- Forms
- ~~~~~
- * ...
- Generic Views
- ~~~~~~~~~~~~~
- * ...
- Internationalization
- ~~~~~~~~~~~~~~~~~~~~
- * ...
- Management Commands
- ~~~~~~~~~~~~~~~~~~~
- * ...
- Migrations
- ~~~~~~~~~~
- * ...
- Models
- ~~~~~~
- * ...
- Requests and Responses
- ~~~~~~~~~~~~~~~~~~~~~~
- * ...
- Serialization
- ~~~~~~~~~~~~~
- * ...
- Signals
- ~~~~~~~
- * ...
- Templates
- ~~~~~~~~~
- * ...
- Tests
- ~~~~~
- * ...
- URLs
- ~~~~
- * ...
- Validators
- ~~~~~~~~~~
- * ...
- .. _backwards-incompatible-2.0:
- Backwards incompatible changes in 2.0
- =====================================
- Database backend API
- --------------------
- * ...
- Miscellaneous
- -------------
- * ...
- .. _deprecated-features-2.0:
- Features deprecated in 2.0
- ==========================
- Miscellaneous
- -------------
- * ...
- .. _removed-features-2.0:
- Features removed in 2.0
- =======================
- These features have reached the end of their deprecation cycle and are removed
- in Django 2.0. See :ref:`deprecated-features-1.9` and
- :ref:`deprecated-features-1.10` for details, including how to remove usage of
- these features.
- * The ``weak`` argument to ``django.dispatch.signals.Signal.disconnect()`` is
- removed.
- * ``django.db.backends.base.BaseDatabaseOperations.check_aggregate_support()``
- is removed.
- * The ``django.forms.extras`` package is removed.
- * The ``assignment_tag`` helper is removed.
- * The ``host`` argument to ``SimpleTestCase.assertsRedirects()`` is removed.
- The compatibility layer which allows absolute URLs to be considered equal to
- relative ones when the path is identical is also removed.
- * ``Field.rel`` and ``Field.remote_field.to`` are removed.
- * The ``on_delete`` argument for ``ForeignKey`` and ``OneToOneField`` are now
- required.
- * ``django.db.models.fields.add_lazy_relation()`` is removed.
- * When time zone support is enabled, database backends that don't support time
- zones no longer convert aware datetimes to naive values in UTC anymore when
- such values are passed as parameters to SQL queries executed outside of the
- ORM, e.g. with ``cursor.execute()``.
- * ``django.contrib.auth.tests.utils.skipIfCustomUser()`` is removed.
- * The ``GeoManager`` and ``GeoQuerySet`` classes are removed.
|