pytz only understands legacy 32bit transition times
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pytz |
Triaged
|
High
|
Unassigned |
Bug Description
When pytz/tzfile.py reads a TZif file, its build_tzinfo function parses only the file's version-1 data, which is limited to 32-bit timestamps that stop working after 2038. In 1995 the TZif file format was expanded to include 64-bit transition times and a POSIX-style TZ string for future timestamps, and tzfile.py needs to support that. Without that support, tzfile.py's build_tzinfo function mishandles some timestamps after 2038 on most platforms. Worse, build_tzinfo mishandles current timestamps on NetBSD 9.0 because NetBSD 9.0 uses the new 'zic -b slim' option that causes TZif files to omit 32-bit data deducible from the 64-bit data that code written since 1995 is supposed to be looking at instead.
Changed in python-tz (Ubuntu): | |
importance: | Undecided → Low |
summary: |
- pytz mishandles Africa/Khartoum in 2017 + pytz only understands legacy 32bit transition times |
description: | updated |
Changed in pytz: | |
status: | New → Triaged |
importance: | Low → High |
I should have written that I see the same bug symptoms on Ubuntu 18.04.4.