#32365: Update timezone implementation to use zoneinfo
------------------------------------------+------------------------
Reporter: Carlton Gibson | Owner: nobody
Type: New feature | Status: new
Component: Utilities | Version: 3.1
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------+------------------------
Python 3.9 introduced `zoneinfo` timezone objects, with backports
available to Python 3.6.
As [https://groups.google.com/g/django-developers/c/PtIyadoC-fI per
discussion on mailing list] we will adopt `zoneinfo` in Django 4.0, using
a `pytz` compatibility shim for those who need it until Django 5.0.
In addition, as per [https://groups.google.com/g/django-
developers/c/cXIyCcjMOds/m/L1H2hlHpCgAJ follow-up discussion], we will
make it possible to use `zoneinfo` objects from Django 3.2, leaving any
handling of DST changes to early-adopter user code. (`make_aware()`'s
`is_dst` likely to be deprecated in Django 4.0 — see follow-up discussion
and [https://github.com/django/django/pull/13877#issuecomment-758769902
comment on initial PR].)
--
Ticket URL: <https://code.djangoproject.com/ticket/32365>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/056.ea4886e09efdd11322f9f40c16d76c65%40djangoproject.com.
