5.0.txt 9.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401
  1. ============================================
  2. Django 5.0 release notes - UNDER DEVELOPMENT
  3. ============================================
  4. *Expected December 2023*
  5. Welcome to Django 5.0!
  6. These release notes cover the :ref:`new features <whats-new-5.0>`, as well as
  7. some :ref:`backwards incompatible changes <backwards-incompatible-5.0>` you'll
  8. want to be aware of when upgrading from Django 4.2 or earlier. We've
  9. :ref:`begun the deprecation process for some features
  10. <deprecated-features-5.0>`.
  11. See the :doc:`/howto/upgrade-version` guide if you're updating an existing
  12. project.
  13. Python compatibility
  14. ====================
  15. Django 5.0 supports Python 3.10, 3.11, and 3.12. We **highly recommend** and
  16. only officially support the latest release of each series.
  17. The Django 4.2.x series is the last to support Python 3.8 and 3.9.
  18. Third-party library support for older version of Django
  19. =======================================================
  20. Following the release of Django 5.0, we suggest that third-party app authors
  21. drop support for all versions of Django prior to 4.2. At that time, you should
  22. be able to run your package's tests using ``python -Wd`` so that deprecation
  23. warnings appear. After making the deprecation warning fixes, your app should be
  24. compatible with Django 5.0.
  25. .. _whats-new-5.0:
  26. What's new in Django 5.0
  27. ========================
  28. Facet filters in the admin
  29. --------------------------
  30. Facet counts are now shown for applied filters in the admin changelist when
  31. toggled on via the UI. This behavior can be changed via the new
  32. :attr:`.ModelAdmin.show_facets` attribute. For more information see
  33. :ref:`facet-filters`.
  34. Minor features
  35. --------------
  36. :mod:`django.contrib.admin`
  37. ~~~~~~~~~~~~~~~~~~~~~~~~~~~
  38. * The new :meth:`.AdminSite.get_log_entries` method allows customizing the
  39. queryset for the site's listed log entries.
  40. :mod:`django.contrib.admindocs`
  41. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  42. * ...
  43. :mod:`django.contrib.auth`
  44. ~~~~~~~~~~~~~~~~~~~~~~~~~~
  45. * The default iteration count for the PBKDF2 password hasher is increased from
  46. 600,000 to 720,000.
  47. * ``AuthenticationMiddleware`` now adds an :meth:`.HttpRequest.auser`
  48. asynchronous method that returns the currently logged-in user.
  49. :mod:`django.contrib.contenttypes`
  50. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  51. * ...
  52. :mod:`django.contrib.gis`
  53. ~~~~~~~~~~~~~~~~~~~~~~~~~
  54. * The new
  55. :class:`ClosestPoint() <django.contrib.gis.db.models.functions.ClosestPoint>`
  56. function returns a 2-dimensional point on the geometry that is closest to
  57. another geometry.
  58. :mod:`django.contrib.messages`
  59. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  60. * ...
  61. :mod:`django.contrib.postgres`
  62. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  63. * The new :attr:`~.ExclusionConstraint.violation_error_code` attribute of
  64. :class:`~django.contrib.postgres.constraints.ExclusionConstraint` allows
  65. customizing the ``code`` of ``ValidationError`` raised during
  66. :ref:`model validation <validating-objects>`.
  67. :mod:`django.contrib.redirects`
  68. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  69. * ...
  70. :mod:`django.contrib.sessions`
  71. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  72. * ...
  73. :mod:`django.contrib.sitemaps`
  74. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  75. * ...
  76. :mod:`django.contrib.sites`
  77. ~~~~~~~~~~~~~~~~~~~~~~~~~~~
  78. * ...
  79. :mod:`django.contrib.staticfiles`
  80. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  81. * ...
  82. :mod:`django.contrib.syndication`
  83. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  84. * ...
  85. Cache
  86. ~~~~~
  87. * ...
  88. CSRF
  89. ~~~~
  90. * ...
  91. Decorators
  92. ~~~~~~~~~~
  93. * ...
  94. Email
  95. ~~~~~
  96. * ...
  97. Error Reporting
  98. ~~~~~~~~~~~~~~~
  99. * ...
  100. File Storage
  101. ~~~~~~~~~~~~
  102. * ...
  103. File Uploads
  104. ~~~~~~~~~~~~
  105. * ...
  106. Forms
  107. ~~~~~
  108. * ...
  109. Generic Views
  110. ~~~~~~~~~~~~~
  111. * ...
  112. Internationalization
  113. ~~~~~~~~~~~~~~~~~~~~
  114. * ...
  115. Logging
  116. ~~~~~~~
  117. * ...
  118. Management Commands
  119. ~~~~~~~~~~~~~~~~~~~
  120. * ...
  121. Migrations
  122. ~~~~~~~~~~
  123. * ...
  124. Models
  125. ~~~~~~
  126. * The new ``create_defaults`` argument of :meth:`.QuerySet.update_or_create`
  127. and :meth:`.QuerySet.aupdate_or_create` methods allows specifying a different
  128. field values for the create operation.
  129. * The new ``violation_error_code`` attribute of
  130. :class:`~django.db.models.BaseConstraint`,
  131. :class:`~django.db.models.CheckConstraint`, and
  132. :class:`~django.db.models.UniqueConstraint` allows customizing the ``code``
  133. of ``ValidationError`` raised during
  134. :ref:`model validation <validating-objects>`.
  135. Requests and Responses
  136. ~~~~~~~~~~~~~~~~~~~~~~
  137. * ...
  138. Security
  139. ~~~~~~~~
  140. * ...
  141. Serialization
  142. ~~~~~~~~~~~~~
  143. * ...
  144. Signals
  145. ~~~~~~~
  146. * The new :meth:`.Signal.asend` and :meth:`.Signal.asend_robust` methods allow
  147. asynchronous signal dispatch. Signal receivers may be synchronous or
  148. asynchronous, and will be automatically adapted to the correct calling style.
  149. Templates
  150. ~~~~~~~~~
  151. * ...
  152. Tests
  153. ~~~~~
  154. * ...
  155. URLs
  156. ~~~~
  157. * ...
  158. Utilities
  159. ~~~~~~~~~
  160. * ...
  161. Validators
  162. ~~~~~~~~~~
  163. * ...
  164. .. _backwards-incompatible-5.0:
  165. Backwards incompatible changes in 5.0
  166. =====================================
  167. Database backend API
  168. --------------------
  169. This section describes changes that may be needed in third-party database
  170. backends.
  171. * ...
  172. Using ``create_defaults__exact`` may now be required with ``QuerySet.update_or_create()``
  173. -----------------------------------------------------------------------------------------
  174. :meth:`.QuerySet.update_or_create` now supports the parameter
  175. ``create_defaults``. As a consequence, any models that have a field named
  176. ``create_defaults`` that are used with an ``update_or_create()`` should specify
  177. the field in the lookup with ``create_defaults__exact``.
  178. Miscellaneous
  179. -------------
  180. * The ``instance`` argument of the undocumented
  181. ``BaseModelFormSet.save_existing()`` method is renamed to ``obj``.
  182. * The undocumented ``django.contrib.admin.helpers.checkbox`` is removed.
  183. .. _deprecated-features-5.0:
  184. Features deprecated in 5.0
  185. ==========================
  186. Miscellaneous
  187. -------------
  188. * The ``DjangoDivFormRenderer`` and ``Jinja2DivFormRenderer`` transitional form
  189. renderers are deprecated.
  190. * Passing positional arguments ``name`` and ``violation_error_message`` to
  191. :class:`~django.db.models.BaseConstraint` is deprecated in favor of
  192. keyword-only arguments.
  193. Features removed in 5.0
  194. =======================
  195. These features have reached the end of their deprecation cycle and are removed
  196. in Django 5.0.
  197. See :ref:`deprecated-features-4.0` for details on these changes, including how
  198. to remove usage of these features.
  199. * The ``SERIALIZE`` test setting is removed.
  200. * The undocumented ``django.utils.baseconv`` module is removed.
  201. * The undocumented ``django.utils.datetime_safe`` module is removed.
  202. * The default value of the ``USE_TZ`` setting is changed from ``False`` to
  203. ``True``.
  204. * The default sitemap protocol for sitemaps built outside the context of a
  205. request is changed from ``'http'`` to ``'https'``.
  206. * The ``extra_tests`` argument for ``DiscoverRunner.build_suite()`` and
  207. ``DiscoverRunner.run_tests()`` is removed.
  208. * The ``django.contrib.postgres.aggregates.ArrayAgg``, ``JSONBAgg``, and
  209. ``StringAgg`` aggregates no longer return ``[]``, ``[]``, and ``''``,
  210. respectively, when there are no rows.
  211. * The ``USE_L10N`` setting is removed.
  212. * The ``USE_DEPRECATED_PYTZ`` transitional setting is removed.
  213. * Support for ``pytz`` timezones is removed.
  214. * The ``is_dst`` argument is removed from:
  215. * ``QuerySet.datetimes()``
  216. * ``django.utils.timezone.make_aware()``
  217. * ``django.db.models.functions.Trunc()``
  218. * ``django.db.models.functions.TruncSecond()``
  219. * ``django.db.models.functions.TruncMinute()``
  220. * ``django.db.models.functions.TruncHour()``
  221. * ``django.db.models.functions.TruncDay()``
  222. * ``django.db.models.functions.TruncWeek()``
  223. * ``django.db.models.functions.TruncMonth()``
  224. * ``django.db.models.functions.TruncQuarter()``
  225. * ``django.db.models.functions.TruncYear()``
  226. * The ``django.contrib.gis.admin.GeoModelAdmin`` and ``OSMGeoAdmin`` classes
  227. are removed.
  228. * The undocumented ``BaseForm._html_output()`` method is removed.
  229. * The ability to return a ``str``, rather than a ``SafeString``, when rendering
  230. an ``ErrorDict`` and ``ErrorList`` is removed.
  231. See :ref:`deprecated-features-4.1` for details on these changes, including how
  232. to remove usage of these features.
  233. * The ``SitemapIndexItem.__str__()`` method is removed.
  234. * The ``CSRF_COOKIE_MASKED`` transitional setting is removed.
  235. * The ``name`` argument of ``django.utils.functional.cached_property()`` is
  236. removed.
  237. * The ``opclasses`` argument of
  238. ``django.contrib.postgres.constraints.ExclusionConstraint`` is removed.
  239. * The undocumented ability to pass ``errors=None`` to
  240. ``SimpleTestCase.assertFormError()`` and ``assertFormsetError()`` is removed.
  241. * ``django.contrib.sessions.serializers.PickleSerializer`` is removed.
  242. * The usage of ``QuerySet.iterator()`` on a queryset that prefetches related
  243. objects without providing the ``chunk_size`` argument is no longer allowed.
  244. * Passing unsaved model instances to related filters is no longer allowed.
  245. * ``created=True`` is required in the signature of
  246. ``RemoteUserBackend.configure_user()`` subclasses.
  247. * Support for logging out via ``GET`` requests in the
  248. ``django.contrib.auth.views.LogoutView`` and
  249. ``django.contrib.auth.views.logout_then_login()`` is removed.
  250. * The ``django.utils.timezone.utc`` alias to ``datetime.timezone.utc`` is
  251. removed.
  252. * Passing a response object and a form/formset name to
  253. ``SimpleTestCase.assertFormError()`` and ``assertFormSetError()`` is no
  254. longer allowed.
  255. * The ``django.contrib.gis.admin.OpenLayersWidget`` is removed.
  256. + The ``django.contrib.auth.hashers.CryptPasswordHasher`` is removed.
  257. * The ``"django/forms/default.html"`` and
  258. ``"django/forms/formsets/default.html"`` templates are removed.
  259. * The default form and formset rendering style is changed to the div-based.
  260. * Passing ``nulls_first=False`` or ``nulls_last=False`` to ``Expression.asc()``
  261. and ``Expression.desc()`` methods, and the ``OrderBy`` expression is no
  262. longer allowed.