#37110: Use `zoneinfo` for validating `TIME_ZONE` setting instead of
`Path("/usr/share/zoneinfo")`
-------------------------------------+-------------------------------------
     Reporter:  jodizzle             |                    Owner:  jodizzle
         Type:                       |                   Status:  closed
  Cleanup/optimization               |
    Component:  Core (Other)         |                  Version:  dev
     Severity:  Normal               |               Resolution:  fixed
     Keywords:  settings             |             Triage Stage:  Ready for
                                     |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls <jacobtylerwalls@…>):

 * resolution:   => fixed
 * status:  assigned => closed

Comment:

 In [changeset:"8c2d3dca633629effad17ccc98730234f740d03f" 8c2d3dca]:
 {{{#!CommitTicketReference repository=""
 revision="8c2d3dca633629effad17ccc98730234f740d03f"
 Fixed #37110 -- Fixed time zone validation when missing zone directory.

 On Unix systems that lack time zone information stored at
 `/usr/share/zoneinfo`, time zones couldn't be validated.

 Python's `zoneinfo` module was introduced in Python 3.9, meaning all
 modern Django versions should support it's use.
 }}}
-- 
Ticket URL: <https://code.djangoproject.com/ticket/37110#comment:10>
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 visit 
https://groups.google.com/d/msgid/django-updates/0107019e940cf4a4-c7f8cccb-855d-4ddf-99b3-6194a618c7a0-000000%40eu-central-1.amazonses.com.

Reply via email to