Author maxnoe
Recipients akira, belopolsky, dlroo, doughellmann, lemburg, maxnoe, vstinner
Date 2020-03-28.18:42:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1585420977.18.0.809026080165.issue23574@roundup.psfhosted.org>
In-reply-to
Content
Could this be revisited?

Especially now that datetime supports `fromisoformat`, as there are valid ISO8601 timestamps in UTC out there, that contain the leap seconds, e.g. files describing when those occured or will occur.

E.g. the NTP Leap second file:
https://kb.meinbergglobal.com/kb/time_sync/ntp/configuration/ntp_leap_second_file

This get's synced on linux to `/usr/share/zoneinfo/leapseconds` and could even be used by python to lookup when leap seconds occured.

The datetime also gained a fold argument, which if it is not wanted to support second values of 60 to at least be able to parse those.

The 60th second of a minute is a reality with our current civil time keeping, so python should be able to handle it.
History
Date User Action Args
2020-03-28 18:42:57maxnoesetrecipients: + maxnoe, lemburg, belopolsky, vstinner, doughellmann, akira, dlroo
2020-03-28 18:42:57maxnoesetmessageid: <1585420977.18.0.809026080165.issue23574@roundup.psfhosted.org>
2020-03-28 18:42:57maxnoelinkissue23574 messages
2020-03-28 18:42:57maxnoecreate