From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Date: Mon, 29 Oct 2018 11:55:08 +0000 (-0700) Subject: bpo-27741: Better wording for datetime.strptime() (GH-9994) X-Git-Tag: v3.7.2rc1~207 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=a02bc719ebc496bc527e9e46de2f2e83f68bfd77;p=thirdparty%2FPython%2Fcpython.git bpo-27741: Better wording for datetime.strptime() (GH-9994) (cherry picked from commit c0799ec973530ad2492bb1d6c7287ffc428f0348) Co-authored-by: Gus Goulart --- diff --git a/Doc/library/datetime.rst b/Doc/library/datetime.rst index a1a60b09cc19..0363111ef55f 100644 --- a/Doc/library/datetime.rst +++ b/Doc/library/datetime.rst @@ -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``