]> git.ipfire.org Git - thirdparty/Python/cpython.git/commitdiff
bpo-27741: Better wording for datetime.strptime() (GH-9994)
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Mon, 29 Oct 2018 11:55:08 +0000 (04:55 -0700)
committerGitHub <noreply@github.com>
Mon, 29 Oct 2018 11:55:08 +0000 (04:55 -0700)
(cherry picked from commit c0799ec973530ad2492bb1d6c7287ffc428f0348)

Co-authored-by: Gus Goulart <augusto@goulart.me>
Doc/library/datetime.rst

index a1a60b09cc19cc37e5e15778a88842f03f6972a5..0363111ef55f2097353d12a664097c743a2462ad 100644 (file)
@@ -2016,7 +2016,9 @@ although not all objects support a :meth:`timetuple` method.
 Conversely, the :meth:`datetime.strptime` class method creates a
 :class:`.datetime` object from a string representing a date and time and a
 corresponding format string. ``datetime.strptime(date_string, format)`` is
-equivalent to ``datetime(*(time.strptime(date_string, format)[0:6]))``.
+equivalent to ``datetime(*(time.strptime(date_string, format)[0:6]))``, except
+when the format includes sub-second components or timezone offset information,
+which are supported in ``datetime.strptime`` but are discarded by ``time.strptime``.
 
 For :class:`.time` objects, the format codes for year, month, and day should not
 be used, as time objects have no such values.  If they're used anyway, ``1900``