Staging
v0.5.1
v0.5.1
https://github.com/python/cpython
Revision 12c178799a23b47c5f8ebc072cbdf09a370649ae authored by Miss Islington (bot) on 04 June 2019, 15:25:16 UTC, committed by GitHub on 04 June 2019, 15:25:16 UTC
* Improve example on tzinfo instances Move from GMTX to TZX when naming the classes, as GMT1 might be rather confusing as seen in the reported issue. In addition, move to UTC over GMT and improve the tzname implementation. * Simplify datetime with tzinfo example Move the example in the documentation to just use timezone.utc and a user defined Kabul timezone rather than having two user defined timezones with DST. Kabul timezone is still interesting as it changes its offset but not based on DST. This is more accurate as the previous example was missing information about the fold attribute. Additionally, implementing the fold attribute was rather complex and probably not relevant enough for the section "datetime with tzinfo". (cherry picked from commit f0b5ae4567637b24035ecda93a3240efc96b6dd9) Co-authored-by: Mario Corchero <mcorcherojim@bloomberg.net>
1 parent cad4ff6
Tip revision: 12c178799a23b47c5f8ebc072cbdf09a370649ae authored by Miss Islington (bot) on 04 June 2019, 15:25:16 UTC
bpo-30699: Improve example on datetime tzinfo instances (GH-4290)
bpo-30699: Improve example on datetime tzinfo instances (GH-4290)
Tip revision: 12c1787
CODE_OF_CONDUCT.rst
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 infrastructure used in the development of Python itself
(e.g. mailing lists, issue trackers, GitHub, etc.).
In general this means everyone is expected to be open, considerate, and
respectful of others no matter what their position is within the project.
Computing file changes ...
