5.0.txt 9.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396
  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 show 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. :mod:`django.contrib.contenttypes`
  48. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  49. * ...
  50. :mod:`django.contrib.gis`
  51. ~~~~~~~~~~~~~~~~~~~~~~~~~
  52. * The new
  53. :class:`ClosestPoint() <django.contrib.gis.db.models.functions.ClosestPoint>`
  54. function returns a 2-dimensional point on the geometry that is closest to
  55. another geometry.
  56. :mod:`django.contrib.messages`
  57. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  58. * ...
  59. :mod:`django.contrib.postgres`
  60. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  61. * The new :attr:`~.ExclusionConstraint.violation_error_code` attribute of
  62. :class:`~django.contrib.postgres.constraints.ExclusionConstraint` allows
  63. customizing the ``code`` of ``ValidationError`` raised during
  64. :ref:`model validation <validating-objects>`.
  65. :mod:`django.contrib.redirects`
  66. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  67. * ...
  68. :mod:`django.contrib.sessions`
  69. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  70. * ...
  71. :mod:`django.contrib.sitemaps`
  72. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  73. * ...
  74. :mod:`django.contrib.sites`
  75. ~~~~~~~~~~~~~~~~~~~~~~~~~~~
  76. * ...
  77. :mod:`django.contrib.staticfiles`
  78. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  79. * ...
  80. :mod:`django.contrib.syndication`
  81. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  82. * ...
  83. Cache
  84. ~~~~~
  85. * ...
  86. CSRF
  87. ~~~~
  88. * ...
  89. Decorators
  90. ~~~~~~~~~~
  91. * ...
  92. Email
  93. ~~~~~
  94. * ...
  95. Error Reporting
  96. ~~~~~~~~~~~~~~~
  97. * ...
  98. File Storage
  99. ~~~~~~~~~~~~
  100. * ...
  101. File Uploads
  102. ~~~~~~~~~~~~
  103. * ...
  104. Forms
  105. ~~~~~
  106. * ...
  107. Generic Views
  108. ~~~~~~~~~~~~~
  109. * ...
  110. Internationalization
  111. ~~~~~~~~~~~~~~~~~~~~
  112. * ...
  113. Logging
  114. ~~~~~~~
  115. * ...
  116. Management Commands
  117. ~~~~~~~~~~~~~~~~~~~
  118. * ...
  119. Migrations
  120. ~~~~~~~~~~
  121. * ...
  122. Models
  123. ~~~~~~
  124. * The new ``create_defaults`` argument of :meth:`.QuerySet.update_or_create`
  125. and :meth:`.QuerySet.aupdate_or_create` methods allows specifying a different
  126. field values for the create operation.
  127. * The new ``violation_error_code`` attribute of
  128. :class:`~django.db.models.BaseConstraint`,
  129. :class:`~django.db.models.CheckConstraint`, and
  130. :class:`~django.db.models.UniqueConstraint` allows customizing the ``code``
  131. of ``ValidationError`` raised during
  132. :ref:`model validation <validating-objects>`.
  133. Requests and Responses
  134. ~~~~~~~~~~~~~~~~~~~~~~
  135. * ...
  136. Security
  137. ~~~~~~~~
  138. * ...
  139. Serialization
  140. ~~~~~~~~~~~~~
  141. * ...
  142. Signals
  143. ~~~~~~~
  144. * ...
  145. Templates
  146. ~~~~~~~~~
  147. * ...
  148. Tests
  149. ~~~~~
  150. * ...
  151. URLs
  152. ~~~~
  153. * ...
  154. Utilities
  155. ~~~~~~~~~
  156. * ...
  157. Validators
  158. ~~~~~~~~~~
  159. * ...
  160. .. _backwards-incompatible-5.0:
  161. Backwards incompatible changes in 5.0
  162. =====================================
  163. Database backend API
  164. --------------------
  165. This section describes changes that may be needed in third-party database
  166. backends.
  167. * ...
  168. Using ``create_defaults__exact`` may now be required with ``QuerySet.update_or_create()``
  169. -----------------------------------------------------------------------------------------
  170. :meth:`.QuerySet.update_or_create` now supports the parameter
  171. ``create_defaults``. As a consequence, any models that have a field named
  172. ``create_defaults`` that are used with an ``update_or_create()`` should specify
  173. the field in the lookup with ``create_defaults__exact``.
  174. Miscellaneous
  175. -------------
  176. * The ``instance`` argument of the undocumented
  177. ``BaseModelFormSet.save_existing()`` method is renamed to ``obj``.
  178. * The undocumented ``django.contrib.admin.helpers.checkbox`` is removed.
  179. .. _deprecated-features-5.0:
  180. Features deprecated in 5.0
  181. ==========================
  182. Miscellaneous
  183. -------------
  184. * The ``DjangoDivFormRenderer`` and ``Jinja2DivFormRenderer`` transitional form
  185. renderers are deprecated.
  186. * Passing positional arguments ``name`` and ``violation_error_message`` to
  187. :class:`~django.db.models.BaseConstraint` is deprecated in favor of
  188. keyword-only arguments.
  189. Features removed in 5.0
  190. =======================
  191. These features have reached the end of their deprecation cycle and are removed
  192. in Django 5.0.
  193. See :ref:`deprecated-features-4.0` for details on these changes, including how
  194. to remove usage of these features.
  195. * The ``SERIALIZE`` test setting is removed.
  196. * The undocumented ``django.utils.baseconv`` module is removed.
  197. * The undocumented ``django.utils.datetime_safe`` module is removed.
  198. * The default value of the ``USE_TZ`` setting is changed from ``False`` to
  199. ``True``.
  200. * The default sitemap protocol for sitemaps built outside the context of a
  201. request is changed from ``'http'`` to ``'https'``.
  202. * The ``extra_tests`` argument for ``DiscoverRunner.build_suite()`` and
  203. ``DiscoverRunner.run_tests()`` is removed.
  204. * The ``django.contrib.postgres.aggregates.ArrayAgg``, ``JSONBAgg``, and
  205. ``StringAgg`` aggregates no longer return ``[]``, ``[]``, and ``''``,
  206. respectively, when there are no rows.
  207. * The ``USE_L10N`` setting is removed.
  208. * The ``USE_DEPRECATED_PYTZ`` transitional setting is removed.
  209. * Support for ``pytz`` timezones is removed.
  210. * The ``is_dst`` argument is removed from:
  211. * ``QuerySet.datetimes()``
  212. * ``django.utils.timezone.make_aware()``
  213. * ``django.db.models.functions.Trunc()``
  214. * ``django.db.models.functions.TruncSecond()``
  215. * ``django.db.models.functions.TruncMinute()``
  216. * ``django.db.models.functions.TruncHour()``
  217. * ``django.db.models.functions.TruncDay()``
  218. * ``django.db.models.functions.TruncWeek()``
  219. * ``django.db.models.functions.TruncMonth()``
  220. * ``django.db.models.functions.TruncQuarter()``
  221. * ``django.db.models.functions.TruncYear()``
  222. * The ``django.contrib.gis.admin.GeoModelAdmin`` and ``OSMGeoAdmin`` classes
  223. are removed.
  224. * The undocumented ``BaseForm._html_output()`` method is removed.
  225. * The ability to return a ``str``, rather than a ``SafeString``, when rendering
  226. an ``ErrorDict`` and ``ErrorList`` is removed.
  227. See :ref:`deprecated-features-4.1` for details on these changes, including how
  228. to remove usage of these features.
  229. * The ``SitemapIndexItem.__str__()`` method is removed.
  230. * The ``CSRF_COOKIE_MASKED`` transitional setting is removed.
  231. * The ``name`` argument of ``django.utils.functional.cached_property()`` is
  232. removed.
  233. * The ``opclasses`` argument of
  234. ``django.contrib.postgres.constraints.ExclusionConstraint`` is removed.
  235. * The undocumented ability to pass ``errors=None`` to
  236. ``SimpleTestCase.assertFormError()`` and ``assertFormsetError()`` is removed.
  237. * ``django.contrib.sessions.serializers.PickleSerializer`` is removed.
  238. * The usage of ``QuerySet.iterator()`` on a queryset that prefetches related
  239. objects without providing the ``chunk_size`` argument is no longer allowed.
  240. * Passing unsaved model instances to related filters is no longer allowed.
  241. * ``created=True`` is required in the signature of
  242. ``RemoteUserBackend.configure_user()`` subclasses.
  243. * Support for logging out via ``GET`` requests in the
  244. ``django.contrib.auth.views.LogoutView`` and
  245. ``django.contrib.auth.views.logout_then_login()`` is removed.
  246. * The ``django.utils.timezone.utc`` alias to ``datetime.timezone.utc`` is
  247. removed.
  248. * Passing a response object and a form/formset name to
  249. ``SimpleTestCase.assertFormError()`` and ``assertFormSetError()`` is no
  250. longer allowed.
  251. * The ``django.contrib.gis.admin.OpenLayersWidget`` is removed.
  252. + The ``django.contrib.auth.hashers.CryptPasswordHasher`` is removed.
  253. * The ``"django/forms/default.html"`` and
  254. ``"django/forms/formsets/default.html"`` templates are removed.
  255. * The default form and formset rendering style is changed to the div-based.
  256. * Passing ``nulls_first=False`` or ``nulls_last=False`` to ``Expression.asc()``
  257. and ``Expression.desc()`` methods, and the ``OrderBy`` expression is no
  258. longer allowed.