DST changes broken in future (2038 and beyond)
Bug #1851355 reported by
direx
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pytz |
Triaged
|
Undecided
|
Unassigned |
Bug Description
I just noticed that DST changes are not calculated at all for dates beyond (and including) 2038.
Example:
>>> tz=pytz.
# This is correct:
>>> tz.localize(
datetime.
# This is wrong:
>>> tz.localize(
datetime.
>>> pytz.__version__
'2019.3'
I have tested a few timezones and this bug seems to affect all of them.
To post a comment you must log in.
I believe this is related to this question from 2015: /answers. launchpad. net/pytz/ +question/ 262216 19T03:14: 07Z.
https:/
where it is stated that pytz as of 2015.6 supports only v1 format, which uses 32-bit integers, which means that it cannot support dates beyond 2038-01-
It would be useful to know when (or if) pytz will support dates beyond 2038. As the current date gets ever closer to 2038, more people will have this same question.