From: R. David Murray Date: Thu, 2 Apr 2009 04:34:04 +0000 (+0000) Subject: Clarify that datetime strftime does not produce leap seconds and datetime X-Git-Tag: v2.7a1~1602 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=d56bab47f1c8432f4d7d3b92d0b8f8320f369fb7;p=python Clarify that datetime strftime does not produce leap seconds and datetime strptime does not accept it in the strftime behavior section of the datetime docs. Closes issue 2568. --- diff --git a/Doc/library/datetime.rst b/Doc/library/datetime.rst index 099627647d..5539c5a940 100644 --- a/Doc/library/datetime.rst +++ b/Doc/library/datetime.rst @@ -1629,8 +1629,12 @@ Notes: the output hour field if the ``%I`` directive is used to parse the hour. (3) - The range really is ``0`` to ``61``; this accounts for leap seconds and the - (very rare) double leap seconds. + 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 :mod:`time` module may produce and does accept leap seconds since + it is based on the Posix standard, but the :mod:`datetime` module + does not accept leap seconds in :func:`strptime` input nor will it + produce them in :func:`strftime` output. (4) When used with the :func:`strptime` function, ``%U`` and ``%W`` are only used in