➜

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 eryksun
Recipients CristiFati, eryksun, iritkatriel, steve.dower, tim.golden, zach.ware
Date 2020-12-01.14:06:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1606831618.96.0.438924821381.issue23946@roundup.psfhosted.org>
In-reply-to
Content 
> The code of posixmodule.c looks very different now.

The conversion code was moved to FILE_TIME_to_time_t_nsec() in Python/fileutils.c. 

time_t is a signed 64-bit integer type, so there's no immediate problem storing 1601-01-01 as the negative (pre-epoch) Unix timestamp -11644473600. But there are indirect problems with using negative Unix timestamps in Windows. In particular, datetime.fromtimestamp doesn't support them:

    >>> datetime.fromtimestamp(-11644473600)
    Traceback (most recent call last):
      File "<stdin>", line 1, in <module>
    OSError: [Errno 22] Invalid argument
History
Date User Action Args
2020-12-01 14:06:58eryksunsetrecipients: + eryksun, tim.golden, zach.ware, steve.dower, CristiFati, iritkatriel
2020-12-01 14:06:58eryksunsetmessageid: <1606831618.96.0.438924821381.issue23946@roundup.psfhosted.org>
2020-12-01 14:06:58eryksunlinkissue23946 messages
2020-12-01 14:06:58eryksuncreate