diff options
| author | Jero Bado <tokidokitalkyou@gmail.com> | 2021-09-22 19:19:20 +0800 |
|---|---|---|
| committer | Carlton Gibson <carlton.gibson@noumenal.es> | 2021-09-22 15:17:40 +0200 |
| commit | 1350187f8e66937a8496434a179f99d38fc368dc (patch) | |
| tree | 4648222a8d8b9458156d6cefebd0b11031682047 | |
| parent | bc0cc82101f0c484e49f49ed3808c97f7eefc44c (diff) | |
[4.0.x] Fixed typo in 4.0 release notes.
Backport of 3f2170f720fe1e2b1030887684c18dc2fc20116b from main
| -rw-r--r-- | docs/releases/4.0.txt | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/releases/4.0.txt b/docs/releases/4.0.txt index 2e097e4701..4bc3fa7678 100644 --- a/docs/releases/4.0.txt +++ b/docs/releases/4.0.txt @@ -48,10 +48,10 @@ current timezone, conversion of datetime instances to the current timezone in forms and templates, as well as operations on aware datetimes in UTC are unaffected. -However, if you are you are working with non-UTC time zones, and using the -``pytz`` ``normalize()`` and ``localize()`` APIs, possibly with the -:setting:`TIME_ZONE <DATABASE-TIME_ZONE>` setting, you will need to audit your -code, since ``pytz`` and ``zoneinfo`` are not entirely equivalent. +However, if you are working with non-UTC time zones, and using the ``pytz`` +``normalize()`` and ``localize()`` APIs, possibly with the :setting:`TIME_ZONE +<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` setting allows continued use of ``pytz`` during the 4.x release cycle. This |