2
0

4.0.txt 13 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475
  1. ============================================
  2. Django 4.0 release notes - UNDER DEVELOPMENT
  3. ============================================
  4. *Expected December 2021*
  5. Welcome to Django 4.0!
  6. These release notes cover the :ref:`new features <whats-new-4.0>`, as well as
  7. some :ref:`backwards incompatible changes <backwards-incompatible-4.0>` you'll
  8. want to be aware of when upgrading from Django 3.2 or earlier. We've
  9. :ref:`begun the deprecation process for some features
  10. <deprecated-features-4.0>`.
  11. See the :doc:`/howto/upgrade-version` guide if you're updating an existing
  12. project.
  13. Python compatibility
  14. ====================
  15. Django 4.0 supports Python 3.8, 3.9, and 3.10. We **highly recommend** and only
  16. officially support the latest release of each series.
  17. The Django 3.2.x series is the last to support Python 3.6 and 3.7.
  18. .. _whats-new-4.0:
  19. What's new in Django 4.0
  20. ========================
  21. Functional unique constraints
  22. -----------------------------
  23. The new :attr:`*expressions <django.db.models.UniqueConstraint.expressions>`
  24. positional argument of
  25. :class:`UniqueConstraint() <django.db.models.UniqueConstraint>` enables
  26. creating functional unique constraints on expressions and database functions.
  27. For example::
  28. from django.db import models
  29. from django.db.models import UniqueConstraint
  30. from django.db.models.functions import Lower
  31. class MyModel(models.Model):
  32. first_name = models.CharField(max_length=255)
  33. last_name = models.CharField(max_length=255)
  34. class Meta:
  35. indexes = [
  36. UniqueConstraint(
  37. Lower('first_name'),
  38. Lower('last_name').desc(),
  39. name='first_last_name_unique',
  40. ),
  41. ]
  42. Functional unique constraints are added to models using the
  43. :attr:`Meta.constraints <django.db.models.Options.constraints>` option.
  44. Minor features
  45. --------------
  46. :mod:`django.contrib.admin`
  47. ~~~~~~~~~~~~~~~~~~~~~~~~~~~
  48. * The ``admin/base.html`` template now has a new block ``header`` which
  49. contains the admin site header.
  50. * The new :meth:`.ModelAdmin.get_formset_kwargs` method allows customizing the
  51. keyword arguments passed to the constructor of a formset.
  52. :mod:`django.contrib.admindocs`
  53. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  54. * The admindocs now allows esoteric setups where :setting:`ROOT_URLCONF` is not
  55. a string.
  56. * The model section of the ``admindocs`` now shows cached properties.
  57. :mod:`django.contrib.auth`
  58. ~~~~~~~~~~~~~~~~~~~~~~~~~~
  59. * The default iteration count for the PBKDF2 password hasher is increased from
  60. 260,000 to 320,000.
  61. * The new
  62. :attr:`LoginView.next_page <django.contrib.auth.views.LoginView.next_page>`
  63. attribute and
  64. :meth:`~django.contrib.auth.views.LoginView.get_default_redirect_url` method
  65. allow customizing the redirect after login.
  66. :mod:`django.contrib.contenttypes`
  67. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  68. * ...
  69. :mod:`django.contrib.gis`
  70. ~~~~~~~~~~~~~~~~~~~~~~~~~
  71. * ...
  72. :mod:`django.contrib.messages`
  73. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  74. * ...
  75. :mod:`django.contrib.postgres`
  76. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  77. * The PostgreSQL backend now supports connecting by a service name. See
  78. :ref:`postgresql-connection-settings` for more details.
  79. :mod:`django.contrib.redirects`
  80. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  81. * ...
  82. :mod:`django.contrib.sessions`
  83. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  84. * ...
  85. :mod:`django.contrib.sitemaps`
  86. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  87. * ...
  88. :mod:`django.contrib.sites`
  89. ~~~~~~~~~~~~~~~~~~~~~~~~~~~
  90. * ...
  91. :mod:`django.contrib.staticfiles`
  92. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  93. * ...
  94. :mod:`django.contrib.syndication`
  95. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  96. * ...
  97. Cache
  98. ~~~~~
  99. * ...
  100. CSRF
  101. ~~~~
  102. * CSRF protection now consults the ``Origin`` header, if present. To facilitate
  103. this, :ref:`some changes <csrf-trusted-origins-changes-4.0>` to the
  104. :setting:`CSRF_TRUSTED_ORIGINS` setting are required.
  105. Decorators
  106. ~~~~~~~~~~
  107. * ...
  108. Email
  109. ~~~~~
  110. * ...
  111. Error Reporting
  112. ~~~~~~~~~~~~~~~
  113. * ...
  114. File Storage
  115. ~~~~~~~~~~~~
  116. * ...
  117. File Uploads
  118. ~~~~~~~~~~~~
  119. * ...
  120. Forms
  121. ~~~~~
  122. * :class:`~django.forms.ModelChoiceField` now includes the provided value in
  123. the ``params`` argument of a raised
  124. :exc:`~django.core.exceptions.ValidationError` for the ``invalid_choice``
  125. error message. This allows custom error messages to use the ``%(value)s``
  126. placeholder.
  127. Generic Views
  128. ~~~~~~~~~~~~~
  129. * ...
  130. Internationalization
  131. ~~~~~~~~~~~~~~~~~~~~
  132. * ...
  133. Logging
  134. ~~~~~~~
  135. * ...
  136. Management Commands
  137. ~~~~~~~~~~~~~~~~~~~
  138. * The :djadmin:`runserver` management command now supports the
  139. :option:`--skip-checks` option.
  140. * On PostgreSQL, :djadmin:`dbshell` now supports specifying a password file.
  141. Migrations
  142. ~~~~~~~~~~
  143. * ...
  144. Models
  145. ~~~~~~
  146. * New :meth:`QuerySet.contains(obj) <.QuerySet.contains>` method returns
  147. whether the queryset contains the given object. This tries to perform the
  148. query in the simplest and fastest way possible.
  149. * The new ``precision`` argument of the
  150. :class:`Round() <django.db.models.functions.Round>` database function allows
  151. specifying the number of decimal places after rounding.
  152. Requests and Responses
  153. ~~~~~~~~~~~~~~~~~~~~~~
  154. * ...
  155. Security
  156. ~~~~~~~~
  157. * ...
  158. Serialization
  159. ~~~~~~~~~~~~~
  160. * ...
  161. Signals
  162. ~~~~~~~
  163. * The new ``stdout`` argument for :func:`~django.db.models.signals.pre_migrate`
  164. and :func:`~django.db.models.signals.post_migrate` signals allows redirecting
  165. output to a stream-like object. It should be preferred over
  166. :py:data:`sys.stdout` and :py:func:`print` when emitting verbose output in
  167. order to allow proper capture when testing.
  168. Templates
  169. ~~~~~~~~~
  170. * ...
  171. Tests
  172. ~~~~~
  173. * The new ``serialized_aliases`` argument of
  174. :func:`django.test.utils.setup_databases` determines which
  175. :setting:`DATABASES` aliases test databases should have their state
  176. serialized to allow usage of the
  177. :ref:`serialized_rollback <test-case-serialized-rollback>` feature.
  178. * Django test runner now supports a :option:`--buffer <test --buffer>` option
  179. with parallel tests.
  180. URLs
  181. ~~~~
  182. * ...
  183. Utilities
  184. ~~~~~~~~~
  185. * ...
  186. Validators
  187. ~~~~~~~~~~
  188. * ...
  189. .. _backwards-incompatible-4.0:
  190. Backwards incompatible changes in 4.0
  191. =====================================
  192. Database backend API
  193. --------------------
  194. This section describes changes that may be needed in third-party database
  195. backends.
  196. * ``DatabaseOperations.year_lookup_bounds_for_date_field()`` and
  197. ``year_lookup_bounds_for_datetime_field()`` methods now take the optional
  198. ``iso_year`` argument in order to support bounds for ISO-8601 week-numbering
  199. years.
  200. :mod:`django.contrib.gis`
  201. -------------------------
  202. * Support for PostGIS 2.3 is removed.
  203. Dropped support for PostgreSQL 9.6
  204. ----------------------------------
  205. Upstream support for PostgreSQL 9.6 ends in November 2021. Django 4.0 supports
  206. PostgreSQL 10 and higher.
  207. Dropped support for Oracle 12.2 and 18c
  208. ---------------------------------------
  209. Upstream support for Oracle 12.2 ends in March 2022 and for Oracle 18c it ends
  210. in June 2021. Django 3.2 will be supported until April 2024. Django 4.0
  211. officially supports Oracle 19c.
  212. .. _csrf-trusted-origins-changes-4.0:
  213. ``CSRF_TRUSTED_ORIGINS`` changes
  214. --------------------------------
  215. Format change
  216. ~~~~~~~~~~~~~
  217. Values in the :setting:`CSRF_TRUSTED_ORIGINS` setting must include the scheme
  218. (e.g. ``'http://'`` or ``'https://'``) instead of only the hostname.
  219. Also, values that started with a dot, must now also include an asterisk before
  220. the dot. For example, change ``'.example.com'`` to ``'https://*.example.com'``.
  221. A system check detects any required changes.
  222. Configuring it may now be required
  223. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  224. As CSRF protection now consults the ``Origin`` header, you may need to set
  225. :setting:`CSRF_TRUSTED_ORIGINS`, particularly if you allow requests from
  226. subdomains by setting :setting:`CSRF_COOKIE_DOMAIN` (or
  227. :setting:`SESSION_COOKIE_DOMAIN` if :setting:`CSRF_USE_SESSIONS` is enabled) to
  228. a value starting with a dot.
  229. Miscellaneous
  230. -------------
  231. * Support for ``cx_Oracle`` < 7.0 is removed.
  232. * To allow serving a Django site on a subpath without changing the value of
  233. :setting:`STATIC_URL`, the leading slash is removed from that setting (now
  234. ``'static/'``) in the default :djadmin:`startproject` template.
  235. * The :class:`~django.contrib.admin.AdminSite` method for the admin ``index``
  236. view is no longer decorated with ``never_cache`` when accessed directly,
  237. rather than via the recommended ``AdminSite.urls`` property, or
  238. ``AdminSite.get_urls()`` method.
  239. * Unsupported operations on a sliced queryset now raise ``TypeError`` instead
  240. of ``AssertionError``.
  241. * The undocumented ``django.test.runner.reorder_suite()`` function is renamed
  242. to ``reorder_tests()``. It now accepts an iterable of tests rather than a
  243. test suite, and returns an iterator of tests.
  244. * Calling ``FileSystemStorage.delete()`` with an empty ``name`` now raises
  245. ``ValueError`` instead of ``AssertionError``.
  246. * Calling ``EmailMultiAlternatives.attach_alternative()`` or
  247. ``EmailMessage.attach()`` with an invalid ``content`` or ``mimetype``
  248. arguments now raise ``ValueError`` instead of ``AssertionError``.
  249. * :meth:`~django.test.SimpleTestCase.assertHTMLEqual` no longer considers a
  250. non-boolean attribute without a value equal to an attribute with the same
  251. name and value.
  252. .. _deprecated-features-4.0:
  253. Features deprecated in 4.0
  254. ==========================
  255. Miscellaneous
  256. -------------
  257. * ``SERIALIZE`` test setting is deprecated as it can be inferred from the
  258. :attr:`~django.test.TestCase.databases` with the
  259. :ref:`serialized_rollback <test-case-serialized-rollback>` option enabled.
  260. Features removed in 4.0
  261. =======================
  262. These features have reached the end of their deprecation cycle and are removed
  263. in Django 4.0.
  264. See :ref:`deprecated-features-3.0` for details on these changes, including how
  265. to remove usage of these features.
  266. * ``django.utils.http.urlquote()``, ``urlquote_plus()``, ``urlunquote()``, and
  267. ``urlunquote_plus()`` are removed.
  268. * ``django.utils.encoding.force_text()`` and ``smart_text()`` are removed.
  269. * ``django.utils.translation.ugettext()``, ``ugettext_lazy()``,
  270. ``ugettext_noop()``, ``ungettext()``, and ``ungettext_lazy()`` are removed.
  271. * ``django.views.i18n.set_language()`` doesn't set the user language in
  272. ``request.session`` (key ``_language``).
  273. * ``alias=None`` is required in the signature of
  274. ``django.db.models.Expression.get_group_by_cols()`` subclasses.
  275. * ``django.utils.text.unescape_entities()`` is removed.
  276. * ``django.utils.http.is_safe_url()`` is removed.
  277. See :ref:`deprecated-features-3.1` for details on these changes, including how
  278. to remove usage of these features.
  279. * The ``PASSWORD_RESET_TIMEOUT_DAYS`` setting is removed.
  280. * The :lookup:`isnull` lookup no longer allows using non-boolean values as the
  281. right-hand side.
  282. * The ``django.db.models.query_utils.InvalidQuery`` exception class is removed.
  283. * The ``django-admin.py`` entry point is removed.
  284. * The ``HttpRequest.is_ajax()`` method is removed.
  285. * Support for the pre-Django 3.1 encoding format of cookies values used by
  286. ``django.contrib.messages.storage.cookie.CookieStorage`` is removed.
  287. * Support for the pre-Django 3.1 password reset tokens in the admin site (that
  288. use the SHA-1 hashing algorithm) is removed.
  289. * Support for the pre-Django 3.1 encoding format of sessions is removed.
  290. * Support for the pre-Django 3.1 ``django.core.signing.Signer`` signatures
  291. (encoded with the SHA-1 algorithm) is removed.
  292. * Support for the pre-Django 3.1 ``django.core.signing.dumps()`` signatures
  293. (encoded with the SHA-1 algorithm) in ``django.core.signing.loads()`` is
  294. removed.
  295. * Support for the pre-Django 3.1 user sessions (that use the SHA-1 algorithm)
  296. is removed.
  297. * The ``get_request`` argument for
  298. ``django.utils.deprecation.MiddlewareMixin.__init__()`` is required and
  299. doesn't accept ``None``.
  300. * The ``providing_args`` argument for ``django.dispatch.Signal`` is removed.
  301. * The ``length`` argument for ``django.utils.crypto.get_random_string()`` is
  302. required.
  303. * The ``list`` message for ``ModelMultipleChoiceField`` is removed.
  304. * Support for passing raw column aliases to ``QuerySet.order_by()`` is removed.
  305. * The ``NullBooleanField`` model field is removed, except for support in
  306. historical migrations.
  307. * ``django.conf.urls.url()`` is removed.
  308. * The ``django.contrib.postgres.fields.JSONField`` model field is removed,
  309. except for support in historical migrations.
  310. * ``django.contrib.postgres.fields.jsonb.KeyTransform`` and
  311. ``django.contrib.postgres.fields.jsonb.KeyTextTransform`` are removed.
  312. * ``django.contrib.postgres.forms.JSONField`` is removed.
  313. * The ``{% ifequal %}`` and ``{% ifnotequal %}`` template tags are removed.
  314. * The ``DEFAULT_HASHING_ALGORITHM`` transitional setting is removed.