Staging
v0.5.1
https://github.com/python/cpython
Revision e527ec8abe0849e784ce100f53c2736986b670ae authored by Paul Ganssle on 18 May 2020, 01:55:11 UTC, committed by GitHub on 18 May 2020, 01:55:11 UTC
This was not specified in the PEP, but it will likely be a frequently requested feature if it's not included.

This includes only the "canonical" zones, not a simple listing of every valid value of `key` that can be passed to `Zoneinfo`, because it seems likely that that's what people will want.
1 parent 9681953
Raw File
Tip revision: e527ec8abe0849e784ce100f53c2736986b670ae authored by Paul Ganssle on 18 May 2020, 01:55:11 UTC
bpo-40536: Add zoneinfo.available_timezones (GH-20158)
Tip revision: e527ec8
CODE_OF_CONDUCT.md
# Code of Conduct

Please note that all interactions on
[Python Software Foundation](https://www.python.org/psf-landing/)-supported
infrastructure is [covered](https://www.python.org/psf/records/board/minutes/2014-01-06/#management-of-the-psfs-web-properties)
by the [PSF Code of Conduct](https://www.python.org/psf/codeofconduct/),
which includes all the infrastructure used in the development of Python itself
(e.g. mailing lists, issue trackers, GitHub, etc.).

In general, this means that everyone is expected to be **open**, **considerate**, and
**respectful** of others no matter what their position is within the project.

back to top