➜

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 martin.panter
Recipients belopolsky, eitan.adler, martin.panter, tim.peters
Date 2018-05-20.00:13:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1526775204.37.0.682650639539.issue33579@psf.upfronthosting.co.za>
In-reply-to
Content 
According to Wikipedia, there were 24 leap seconds before Feb 2009. So my guess is Eitan’s “gmtime” implementation is calculating the date as if the timestamp (1234567899) includes leap seconds, as in <https://en.wikipedia.org/wiki/Unix_time#TAI-based_variant>. But according to Posix, the calculation should be for exactly 86400 timestamp seconds per day, and it should not adjust for leap seconds.
History
Date User Action Args
2018-05-20 00:13:24martin.pantersetrecipients: + martin.panter, tim.peters, belopolsky, eitan.adler
2018-05-20 00:13:24martin.pantersetmessageid: <1526775204.37.0.682650639539.issue33579@psf.upfronthosting.co.za>
2018-05-20 00:13:24martin.panterlinkissue33579 messages
2018-05-20 00:13:23martin.pantercreate