diff options
| author | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2023-01-09 09:03:38 +0100 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2023-01-17 11:49:15 +0100 |
| commit | e6f82438d4e3750e8d299bfd79dac98eebe9f1e0 (patch) | |
| tree | 4ee0cbf2c0be9822416aa3d65105f35a9784fd94 /docs/releases/4.0.txt | |
| parent | 8d98f99a4ab5de6f2c730399f53eba8bf6bea470 (diff) | |
| download | django-e6f82438d4e3750e8d299bfd79dac98eebe9f1e0.tar.gz | |
Refs #32365 -- Removed support for pytz timezones per deprecation timeline.
Diffstat (limited to 'docs/releases/4.0.txt')
| -rw-r--r-- | docs/releases/4.0.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/releases/4.0.txt b/docs/releases/4.0.txt index d64e74941c..74dd4dbb93 100644 --- a/docs/releases/4.0.txt +++ b/docs/releases/4.0.txt @@ -53,7 +53,7 @@ However, if you are working with non-UTC time zones, and using the ``pytz`` <DATABASE-TIME_ZONE>` setting, you will need to audit your code, since ``pytz`` and ``zoneinfo`` are not entirely equivalent. -To give time for such an audit, the transitional :setting:`USE_DEPRECATED_PYTZ` +To give time for such an audit, the transitional ``USE_DEPRECATED_PYTZ`` setting allows continued use of ``pytz`` during the 4.x release cycle. This setting will be removed in Django 5.0. @@ -62,7 +62,7 @@ author, can be used to assist with the migration from ``pytz``. This package provides shims to help you safely remove ``pytz``, and has a detailed `migration guide`_ showing how to move to the new ``zoneinfo`` APIs. -Using `pytz_deprecation_shim`_ and the :setting:`USE_DEPRECATED_PYTZ` +Using `pytz_deprecation_shim`_ and the ``USE_DEPRECATED_PYTZ`` transitional setting is recommended if you need a gradual update path. .. _pytz_deprecation_shim: https://pytz-deprecation-shim.readthedocs.io/en/latest/index.html |