@@ -2048,6 +2048,9 @@ For :class:`date` objects, the format codes for hours, minutes, seconds, and
|
2048 | 2048 | microseconds should not be used, as :class:`date` objects have no such |
2049 | 2049 | values. If they're used anyway, ``0`` is substituted for them. |
2050 | 2050 | |
| 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 | + |
2051 | 2054 | The full set of format codes supported varies across platforms, because Python |
2052 | 2055 | calls the platform C library's :func:`strftime` function, and platform |
2053 | 2056 | variations are common. To see the full set of format codes supported on your |
@@ -2282,3 +2285,4 @@ Notes:
|
2282 | 2285 | .. rubric:: Footnotes |
2283 | 2286 | |
2284 | 2287 | .. [#] 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. |