This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author SilentGhost
Recipients SilentGhost, belopolsky, jamercee, p-ganssle
Date 2020-05-25.18:18:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1590430708.78.0.765752282395.issue40771@roundup.psfhosted.org>
In-reply-to
Content
You seem to have read the docs, so I'm a bit confused why you think that is a bug. According to https://docs.python.org/3/library/datetime.html#datetime.datetime.fromtimestamp

> fromtimestamp() may raise OverflowError, if the timestamp is out of the range of values supported by the platform C localtime() or gmtime() functions, and OSError on localtime() or gmtime() failure.

This looks exactly like this type of error. It is completely irrelevant whether Windows supports a timestamp this far in the future, clearly platform's localtime() / gmtime() do not. Constructing datetime object in Python does not require such system calls and their limitations no longer apply.
History
Date User Action Args
2020-05-25 18:18:28SilentGhostsetrecipients: + SilentGhost, belopolsky, jamercee, p-ganssle
2020-05-25 18:18:28SilentGhostsetmessageid: <1590430708.78.0.765752282395.issue40771@roundup.psfhosted.org>
2020-05-25 18:18:28SilentGhostlinkissue40771 messages
2020-05-25 18:18:28SilentGhostcreate