* PEP-615 consistent terminology
It repeatedly refers to a ZoneInfo object as a "file", confusing it with either the file it was constructed from, or the IO object representing the file.
* Further clarification of caching implications
* Mark "use the datetime module" as rejected.
There did not seem to be any concerns about having `zoneinfo` live in
a separate module.
* Add additional rationale to updating behavior
* Update Post-History
* Change fallback behavior for __str__
Per Petr's suggestion in the discourse thread. Turns out this was
basically what the reference implementation does anyway.
* Rename `set_tzpath` to `reset_tzpath`
* Adjust TZPATH strategy
Partially in response to Petr's comment on the discourse thread, and
partially from further reflection.
* Fix typo in RFC 8536 reference
* Add path traversal to security implications.
Seems like a minor concern, but possibly worth noting.
* Add IANA Time Zone Support PEP
* Add section rejecting Windows native time zones
* Normalize code-block and drop python3
Apparently this is rendered without pygments support, which is causing
the build to fail.
* Add justification for a separate module
* Clean up and reorganize footnotes and citations
This adds headlines / citations for each footnote, rather than bare
links, and tries to put them in a more logical grouping, and makes
them all render without issues.
* Add / adjust proposal targets
* Add justification for set_tzpath
Basically, "people are going to do this anyway, might as well have them
use a function that we can at least deprecate if it causes major
problems."
* Add citation for rearguard format
* Fix typos and formatting in abstract
Fixes a few typos and reformats the abstract using semantic newlines.
* Update location of reference implementation
* Tweaks to motivation section
* Clarify wording about PEP organization
* Tweaks to section on the ZoneInfo class
This adjusts the wording and fixes typos in the constructors and pickle
sections.
* Tweaks 'Sources for time zone data'
These are typos, clarifications and wording adjustments in the section
on time zone data sources.
* Use semantic newlines in 'Security implications'
* Clarify what 'no special verification' means
* Add clarification to custom compiler section
* Tweaks to wording on 'tzdata' in the standard library
* Tweaks to Windows section
* Adjust the justification for rejecting pytz
* Add quotation marks around blog titles
* Abandon semantic newlines
* Rename title
* Move module name into 'Open issues'
* Comment out temporarily unused headers
* Add open issue about TZPATH structure
* Remove erroneous blockquotes
* Add discourse link and Post-History
James Howe
Marius Gedminas
Paul Ganssle