[issue18718] datetime documentation contradictory on leap second support

David Wolever added the comment: D'oh, yes, it can (and I've closed it now). -- status: pending -> closed ___ Python tracker ___ ___ P

[issue18718] datetime documentation contradictory on leap second support

Ezio Melotti added the comment: Can this be closed? -- nosy: +ezio.melotti resolution: -> fixed stage: -> committed/rejected status: open -> pending type: -> enhancement ___ Python tracker __

[issue18718] datetime documentation contradictory on leap second support

Roundup Robot added the comment: New changeset 5063dab96843 by David Wolever in branch '2.7': Issue #18718: datetime documentation contradictory on leap second support http://hg.python.org/cpython/rev/5063dab96843 -- nosy: +python-dev ___ Python track

[issue18718] datetime documentation contradictory on leap second support

Alexander Belopolsky added the comment: +1 :-) -- nosy: +belopolsky ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscr

[issue18718] datetime documentation contradictory on leap second support

David Wolever added the comment: Here's the relevant diff. Will commit on a +1. diff --git a/Doc/library/datetime.rst b/Doc/library/datetime.rst --- a/Doc/library/datetime.rst +++ b/Doc/library/datetime.rst @@ -1664,7 +1664,7 @@ | ``%M``| Minute as a zero-padded| 00, 01, ..., 59

[issue18718] datetime documentation contradictory on leap second support

New submission from David Wolever: The documentation for the `%S` formatter suggests that it supports leap seconds, but the footnote contradicts that: > 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 t