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 p-ganssle
Recipients Tiger-222, p-ganssle, steve.dower, vstinner
Date 2019-11-01.14:54:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1572620086.44.0.449374666296.issue36439@roundup.psfhosted.org>
In-reply-to
Content
This has been coming up in a few different contexts lately, so I think it would be really good if we could get some sort of fix for it.

One option is to implement our own versions of these APIs for use in Windows, but a thought occurred to me recently: we have not investigated the possibility of seeing if Microsoft would be willing to either add support for negative timestamps in their localtime() or gmtime() implementations or add a new API that *does* support negative timestamps. It would also be good to rule out the possibility that such APIs already exist but we just don't know about them (preliminary googling doesn't show anything, though possibly something can be done with the Win32 APIs? Not sure how or if those work in C and how big a lift it would be to maintain compatibility if can switch: https://docs.microsoft.com/en-us/windows/win32/sysinfo/time-functions?redirectedfrom=MSDN ).

Adding Steve Dower to the nosy list in case he can shed some light onto the possibility of native support.
History
Date User Action Args
2019-11-01 14:54:46p-gansslesetrecipients: + p-ganssle, vstinner, steve.dower, Tiger-222
2019-11-01 14:54:46p-gansslesetmessageid: <1572620086.44.0.449374666296.issue36439@roundup.psfhosted.org>
2019-11-01 14:54:46p-gansslelinkissue36439 messages
2019-11-01 14:54:46p-gansslecreate