Skip to content

Commit 56027cc

Browse files
toanantcsabella
authored andcommitted
bpo-19376: Added doc mentioning datetime.strptime() without a year fails for Feb 29. (GH-10243)
1 parent abea73b commit 56027cc

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

Doc/library/datetime.rst

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2048,6 +2048,9 @@ For :class:`date` objects, the format codes for hours, minutes, seconds, and
20482048
microseconds should not be used, as :class:`date` objects have no such
20492049
values. If they're used anyway, ``0`` is substituted for them.
20502050

2051+
For the :meth:`datetime.strptime` class method, the default value is ``1900-01-01T00:00:00.000``:
2052+
any components not specified in the format string will be pulled from the default value. [#]_
2053+
20512054
The full set of format codes supported varies across platforms, because Python
20522055
calls the platform C library's :func:`strftime` function, and platform
20532056
variations are common. To see the full set of format codes supported on your
@@ -2282,3 +2285,4 @@ Notes:
22822285
.. rubric:: Footnotes
22832286

22842287
.. [#] If, that is, we ignore the effects of Relativity
2288+
.. [#] Passing ``datetime.strptime('Feb 29', '%b %d')`` will fail since ``1900`` is not a leap year.

0 commit comments

Comments
 (0)