From 941b8cc6865bf68bdfe4460dca5fb626b7db5904 Mon Sep 17 00:00:00 2001 From: Abhishek Kumar Singh Date: Tue, 30 Oct 2018 20:48:23 +0530 Subject: [PATCH] bpo-19376: Added doc. Added doc mentioning `datetime.strptime()` without a year fails for Feb 29. --- Doc/library/datetime.rst | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Doc/library/datetime.rst b/Doc/library/datetime.rst index 0363111ef55f20..2bfbff276a53ee 100644 --- a/Doc/library/datetime.rst +++ b/Doc/library/datetime.rst @@ -2028,6 +2028,9 @@ For :class:`date` objects, the format codes for hours, minutes, seconds, and microseconds should not be used, as :class:`date` objects have no such values. If they're used anyway, ``0`` is substituted for them. +For the :meth:`datetime.strptime` class method, the default value is ``1900-01-01T00:00:00.000``: +any components not specified in the format string will be pulled from the default value. [#]_ + The full set of format codes supported varies across platforms, because Python calls the platform C library's :func:`strftime` function, and platform variations are common. To see the full set of format codes supported on your @@ -2256,3 +2259,4 @@ Notes: .. rubric:: Footnotes .. [#] If, that is, we ignore the effects of Relativity +.. [#] Passing ``datetime.strptime('Feb 29', '%b %d')`` will fail since ``1900`` is not a leap year.