[issue2568] Seconds range in time unit

Alexander Belopolsky added the comment: Committed in revision 87910. -- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker _

[issue2568] Seconds range in time unit

Alexander Belopolsky added the comment: The C89 draft as available through a Wikipedia link, http://flash-gordon.me.uk/ansi.c.txt, specifies tm_sec range as [0, 60]. Although it looks like the range has been extended in the published version. A discussion on comp.std.c describes the situati

[issue2568] Seconds range in time unit

Alexander Belopolsky added the comment: I am reopening this issue because the following note is still not entirely correct: """ The range really is 0 to 61; according to the Posix standard this accounts for leap seconds and the (very rare) double leap seconds. The time module may produce and

[issue2568] Seconds range in time unit

R. David Murray added the comment: Doc patch applied in r71037. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___

[issue2568] Seconds range in time unit

R. David Murray added the comment: 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

[issue2568] Seconds range in time unit

Changes by Georg Brandl <[EMAIL PROTECTED]>: -- assignee: georg.brandl -> __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list

[issue2568] Seconds range in time unit

Georg Brandl <[EMAIL PROTECTED]> added the comment: Okay, sorry that I made uninformed guesses :) __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list

[issue2568] Seconds range in time unit

Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: On Wed, Apr 9, 2008 at 2:49 PM, Georg Brandl <[EMAIL PROTECTED]> wrote: > Isn't the bug here rather that strptime doesn't allow leap seconds? This is not specific to strptime. The datetime module does not allow leap seconds: Traceba

[issue2568] Seconds range in time unit

Georg Brandl <[EMAIL PROTECTED]> added the comment: Isn't the bug here rather that strptime doesn't allow leap seconds? __ Tracker <[EMAIL PROTECTED]> __ ___

[issue2568] Seconds range in time unit

Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: On Mon, Apr 7, 2008 at 3:42 PM, Anton Fedorov <[EMAIL PROTECTED]> wrote: > There no leap second in 2000th. I was just too lazy too look up the leap second year, but datetime module knows nothing about leap seconds, so I did not expect

[issue2568] Seconds range in time unit

Anton Fedorov <[EMAIL PROTECTED]> added the comment: There no leap second in 2000th. But correct time request fails: >>> datetime.strptime('19951231T235960', '%Y%m%dT%H%M%S') Traceback (most recent call last): File "", line 1, in ValueError: second must be in 0..59 ___

[issue2568] Seconds range in time unit

Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: On the other hand, the time module allows full [00,61] range: >>> [time.strftime('%S',time.strptime(x, '%S')) for x in ('00', '61')] ['00', '61'] so this is implementation rather than documentation issue.

[issue2568] Seconds range in time unit

Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: OP does not have the reference, but the issue is apparently in the time and datetime modules documentation: http://docs.python.org/dev/library/time.html#time.strftime http://docs.python.org/dev/library/datetime.html#strftime-behavior N

[issue2568] Seconds range in time unit

New submission from Anton Fedorov <[EMAIL PROTECTED]>: "%S Second as a decimal number [00,61]. (2) (2) The range really is 0 to 61; this accounts for leap seconds and the (very rare) double leap seconds." That is wrong. There NEVER can be two leap seconds in one moment, since UTC time