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 r.david.murray
Recipients belopolsky, datacompboy, georg.brandl, r.david.murray
Date 2009-03-29.02:55:53
SpamBayes Score 4.07206e-06
Marked as misclassified No
Message-id <1238295356.18.0.163078657974.issue2568@psf.upfronthosting.co.za>
In-reply-to
Content
The 'double leap second' issue has been around a long time and is part
of the Posix standard (for some background see
http://www.ucolick.org/~sla/leapsecs/onlinebib.html, specifically the
section named 'Unix system time and the POSIX standard').  This document
notes that the double leap second was still in the standard in 1997, and
according to Wikipedia that is after the last revision of the standard,
so presumably it is still there.

Therefore the time documentation of strftime is correct, since my
understanding is that time is a wrapper around the Posix time functions.
 The datetime docs, on the other hand, are misleading in the strftime
documentation.  I've attached a doc patch to have the note clarify that
datetime does not consume or produce leap seconds.
History
Date User Action Args
2009-03-29 02:55:56r.david.murraysetrecipients: + r.david.murray, georg.brandl, belopolsky, datacompboy
2009-03-29 02:55:56r.david.murraysetmessageid: <1238295356.18.0.163078657974.issue2568@psf.upfronthosting.co.za>
2009-03-29 02:55:54r.david.murraylinkissue2568 messages
2009-03-29 02:55:54r.david.murraycreate