➜

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 vstinner
Recipients Dennis Sweeney, SD, eryksun, lunixbochs2, miss-islington, ned.deily, paul.moore, pitrou, steve.dower, tim.golden, vstinner, zach.ware
Date 2021-06-14.11:05:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1623668730.43.0.488098983254.issue41299@roundup.psfhosted.org>
In-reply-to
Content 
I'm fine with adding _PyTime_Init() again, and maybe only implement checks on Windows.

On Linux, I only saw a single failure in _PyTime_Init() once, when Python was run in a sandbox, and the time syscalls were not allowed. It was a corner case about the new 64-bit time_t syscalls on a 32-bit system (container):
https://bugzilla.redhat.com/show_bug.cgi?id=1887445
History
Date User Action Args
2021-06-14 11:05:30vstinnersetrecipients: + vstinner, paul.moore, pitrou, tim.golden, ned.deily, zach.ware, eryksun, steve.dower, miss-islington, Dennis Sweeney, SD, lunixbochs2
2021-06-14 11:05:30vstinnersetmessageid: <1623668730.43.0.488098983254.issue41299@roundup.psfhosted.org>
2021-06-14 11:05:30vstinnerlinkissue41299 messages
2021-06-14 11:05:30vstinnercreate