| @@ -2031,6 +2031,9 @@ For :class:`date` objects, the format codes for hours, minutes, seconds, and |
|
|
| 2031 |
2031 |
microseconds should not be used, as :class:`date` objects have no such |
| 2032 |
2032 |
values. If they're used anyway, ``0`` is substituted for them. |
| 2033 |
2033 |
|
|
2034 |
+For the :meth:`datetime.strptime` class method, the default value is ``1900-01-01T00:00:00.000``: |
|
2035 |
+any components not specified in the format string will be pulled from the default value. [#]_ |
|
2036 |
+ |
| 2034 |
2037 |
The full set of format codes supported varies across platforms, because Python |
| 2035 |
2038 |
calls the platform C library's :func:`strftime` function, and platform |
| 2036 |
2039 |
variations are common. To see the full set of format codes supported on your |
| @@ -2265,3 +2268,4 @@ Notes: |
|
|
| 2265 |
2268 |
.. rubric:: Footnotes |
| 2266 |
2269 |
|
| 2267 |
2270 |
.. [#] If, that is, we ignore the effects of Relativity |
|
2271 |
+.. [#] Passing ``datetime.strptime('Feb 29', '%b %d')`` will fail since ``1900`` is not a leap year. |