4.2.txt 9.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390
  1. ============================================
  2. Django 4.2 release notes - UNDER DEVELOPMENT
  3. ============================================
  4. *Expected April 2023*
  5. Welcome to Django 4.2!
  6. These release notes cover the :ref:`new features <whats-new-4.2>`, as well as
  7. some :ref:`backwards incompatible changes <backwards-incompatible-4.2>` you'll
  8. want to be aware of when upgrading from Django 4.1 or earlier. We've
  9. :ref:`begun the deprecation process for some features
  10. <deprecated-features-4.2>`.
  11. See the :doc:`/howto/upgrade-version` guide if you're updating an existing
  12. project.
  13. Python compatibility
  14. ====================
  15. Django 4.2 supports Python 3.8, 3.9, 3.10, and 3.11. We **highly recommend**
  16. and only officially support the latest release of each series.
  17. .. _whats-new-4.2:
  18. What's new in Django 4.2
  19. ========================
  20. Minor features
  21. --------------
  22. :mod:`django.contrib.admin`
  23. ~~~~~~~~~~~~~~~~~~~~~~~~~~~
  24. * The light or dark color theme of the admin can now be toggled in the UI, as
  25. well as being set to follow the system setting.
  26. * The admin's font stack now prefers system UI fonts and no longer requires
  27. downloading fonts. Additionally, CSS variables are available to more easily
  28. override the default font families.
  29. * The :source:`admin/delete_confirmation.html
  30. <django/contrib/admin/templates/admin/delete_confirmation.html>` template now
  31. has some additional blocks and scripting hooks to ease customization.
  32. :mod:`django.contrib.admindocs`
  33. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  34. * ...
  35. :mod:`django.contrib.auth`
  36. ~~~~~~~~~~~~~~~~~~~~~~~~~~
  37. * The default iteration count for the PBKDF2 password hasher is increased from
  38. 390,000 to 480,000.
  39. :mod:`django.contrib.contenttypes`
  40. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  41. * ...
  42. :mod:`django.contrib.gis`
  43. ~~~~~~~~~~~~~~~~~~~~~~~~~
  44. * The :doc:`GeoJSON serializer </ref/contrib/gis/serializers>` now outputs the
  45. ``id`` key for serialized features, which defaults to the primary key of
  46. objects.
  47. * The :class:`~django.contrib.gis.gdal.GDALRaster` class now supports
  48. :class:`pathlib.Path`.
  49. * The :class:`~django.contrib.gis.geoip2.GeoIP2` class now supports ``.mmdb``
  50. files downloaded from DB-IP.
  51. * The OpenLayers template widget no longer includes inline CSS (which also
  52. removes the former ``map_css`` block) to better comply with a strict Content
  53. Security Policy.
  54. :mod:`django.contrib.messages`
  55. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  56. * ...
  57. :mod:`django.contrib.postgres`
  58. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  59. * The new :lookup:`trigram_strict_word_similar` lookup, and the
  60. :class:`TrigramStrictWordSimilarity()
  61. <django.contrib.postgres.search.TrigramStrictWordSimilarity>` and
  62. :class:`TrigramStrictWordDistance()
  63. <django.contrib.postgres.search.TrigramStrictWordDistance>` expressions allow
  64. using trigram strict word similarity.
  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. * :class:`~django.forms.ModelForm` now accepts the new ``Meta`` option
  107. ``formfield_callback`` to customize form fields.
  108. * :func:`~django.forms.models.modelform_factory` now respects the
  109. ``formfield_callback`` attribute of the ``form``’s ``Meta``.
  110. Generic Views
  111. ~~~~~~~~~~~~~
  112. * ...
  113. Internationalization
  114. ~~~~~~~~~~~~~~~~~~~~
  115. * Added support and translations for the Central Kurdish (Sorani) language.
  116. Logging
  117. ~~~~~~~
  118. * ...
  119. Management Commands
  120. ~~~~~~~~~~~~~~~~~~~
  121. * :djadmin:`makemessages` command now supports locales with private sub-tags
  122. such as ``nl_NL-x-informal``.
  123. * The new :option:`makemigrations --update` option merges model changes into
  124. the latest migration and optimizes the resulting operations.
  125. Migrations
  126. ~~~~~~~~~~
  127. * Migrations now support serialization of ``enum.Flag`` objects.
  128. Models
  129. ~~~~~~
  130. * ``QuerySet`` now extensively supports filtering against
  131. :ref:`window-functions` with the exception of disjunctive filter lookups
  132. against window functions when performing aggregation.
  133. * :meth:`~.QuerySet.prefetch_related` now supports
  134. :class:`~django.db.models.Prefetch` objects with sliced querysets.
  135. * :ref:`Registering lookups <lookup-registration-api>` on
  136. :class:`~django.db.models.Field` instances is now supported.
  137. Requests and Responses
  138. ~~~~~~~~~~~~~~~~~~~~~~
  139. * ...
  140. Security
  141. ~~~~~~~~
  142. * ...
  143. Serialization
  144. ~~~~~~~~~~~~~
  145. * ...
  146. Signals
  147. ~~~~~~~
  148. * ...
  149. Templates
  150. ~~~~~~~~~
  151. * ...
  152. Tests
  153. ~~~~~
  154. * ...
  155. URLs
  156. ~~~~
  157. * ...
  158. Utilities
  159. ~~~~~~~~~
  160. * The new ``encoder`` parameter for :meth:`django.utils.html.json_script`
  161. function allows customizing a JSON encoder class.
  162. * The private internal vendored copy of ``urllib.parse.urlsplit()`` now strips
  163. ``'\r'``, ``'\n'``, and ``'\t'`` (see :cve:`2022-0391` and :bpo:`43882`).
  164. This is to protect projects that may be incorrectly using the internal
  165. ``url_has_allowed_host_and_scheme()`` function, instead of using one of the
  166. documented functions for handling URL redirects. The Django functions were
  167. not affected.
  168. Validators
  169. ~~~~~~~~~~
  170. * ...
  171. .. _backwards-incompatible-4.2:
  172. Backwards incompatible changes in 4.2
  173. =====================================
  174. Database backend API
  175. --------------------
  176. This section describes changes that may be needed in third-party database
  177. backends.
  178. * ...
  179. Dropped support for MariaDB 10.3
  180. --------------------------------
  181. Upstream support for MariaDB 10.3 ends in May 2023. Django 4.2 supports MariaDB
  182. 10.4 and higher.
  183. Dropped support for MySQL 5.7
  184. -----------------------------
  185. Upstream support for MySQL 5.7 ends in October 2023. Django 4.2 supports MySQL
  186. 8 and higher.
  187. Dropped support for PostgreSQL 11
  188. ---------------------------------
  189. Upstream support for PostgreSQL 11 ends in November 2023. Django 4.2 supports
  190. PostgreSQL 12 and higher.
  191. Miscellaneous
  192. -------------
  193. * The undocumented ``SimpleTemplateResponse.rendering_attrs`` and
  194. ``TemplateResponse.rendering_attrs`` are renamed to ``non_picklable_attrs``.
  195. * The undocumented ``django.http.multipartparser.parse_header()`` function is
  196. removed. Use ``django.utils.http.parse_header_parameters()`` instead.
  197. * :ttag:`{% blocktranslate asvar … %}<blocktranslate>` result is now marked as
  198. safe for (HTML) output purposes.
  199. .. _deprecated-features-4.2:
  200. Features deprecated in 4.2
  201. ==========================
  202. ``index_together`` option is deprecated in favor of ``indexes``
  203. ---------------------------------------------------------------
  204. The :attr:`Meta.index_together <django.db.models.Options.index_together>`
  205. option is deprecated in favor of the :attr:`~django.db.models.Options.indexes`
  206. option.
  207. Migrating existing ``index_together`` should be handled as a migration. For
  208. example::
  209. class Author(models.Model):
  210. rank = models.IntegerField()
  211. name = models.CharField(max_length=30)
  212. class Meta:
  213. index_together = [["rank", "name"]]
  214. Should become::
  215. class Author(models.Model):
  216. rank = models.IntegerField()
  217. name = models.CharField(max_length=30)
  218. class Meta:
  219. indexes = [models.Index(fields=["rank", "name"])]
  220. Running the :djadmin:`makemigrations` command will generate a migration
  221. containing a :class:`~django.db.migrations.operations.RenameIndex` operation
  222. which will rename the existing index.
  223. The ``AlterIndexTogether`` migration operation is now officially supported only
  224. for pre-Django 4.2 migration files. For backward compatibility reasons, it's
  225. still part of the public API, and there's no plan to deprecate or remove it,
  226. but it should not be used for new migrations. Use
  227. :class:`~django.db.migrations.operations.AddIndex` and
  228. :class:`~django.db.migrations.operations.RemoveIndex` operations instead.
  229. Miscellaneous
  230. -------------
  231. * The ``BaseUserManager.make_random_password()`` method is deprecated. See
  232. `recipes and best practices
  233. <https://docs.python.org/3/library/secrets.html#recipes-and-best-practices>`_
  234. for using Python's :py:mod:`secrets` module to generate passwords.
  235. * The ``length_is`` template filter is deprecated in favor of :tfilter:`length`
  236. and the ``==`` operator within an :ttag:`{% if %}<if>` tag. For example
  237. .. code-block:: html+django
  238. {% if value|length == 4 %}…{% endif %}
  239. {% if value|length == 4 %}True{% else %}False{% endif %}
  240. instead of:
  241. .. code-block:: html+django
  242. {% if value|length_is:4 %}…{% endif %}
  243. {{ value|length_is:4 }}
  244. * ``django.contrib.auth.hashers.SHA1PasswordHasher``,
  245. ``django.contrib.auth.hashers.UnsaltedSHA1PasswordHasher``, and
  246. ``django.contrib.auth.hashers.UnsaltedMD5PasswordHasher`` are deprecated.
  247. * ``django.contrib.postgres.fields.CICharField`` is deprecated in favor of
  248. ``CharField(db_collation="…")`` with a case-insensitive non-deterministic
  249. collation.
  250. * ``django.contrib.postgres.fields.CIEmailField`` is deprecated in favor of
  251. ``EmailField(db_collation="…")`` with a case-insensitive non-deterministic
  252. collation.
  253. * ``django.contrib.postgres.fields.CITextField`` is deprecated in favor of
  254. ``TextField(db_collation="…")`` with a case-insensitive non-deterministic
  255. collation.
  256. * ``django.contrib.postgres.fields.CIText`` mixin is deprecated.
  257. * The ``map_height`` and ``map_width`` attributes of ``BaseGeometryWidget`` are
  258. deprecated, use CSS to size map widgets instead.