From e2b40f4ce954ea3d35a73541029b2253abd9d245 Mon Sep 17 00:00:00 2001 From: "Miss Islington (bot)" <31488909+miss-islington@users.noreply.github.com> Date: Tue, 11 Sep 2018 14:24:53 -0700 Subject: [PATCH] bpo-34365: Update date object documentation (GH-8814) Python 3.x does not fall back to comparing object addresses when comparing two `dt` objects. https://bugs.python.org/issue34365 (cherry picked from commit 9c223794c754408644c16349b85dd27fdba8a926) Co-authored-by: Danish Prakash --- Doc/library/datetime.rst | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/Doc/library/datetime.rst b/Doc/library/datetime.rst index 53c181c4014..22582476cf9 100644 --- a/Doc/library/datetime.rst +++ b/Doc/library/datetime.rst @@ -526,10 +526,9 @@ Notes: (4) In other words, ``date1 < date2`` if and only if ``date1.toordinal() < - date2.toordinal()``. In order to stop comparison from falling back to the - default scheme of comparing object addresses, date comparison normally raises - :exc:`TypeError` if the other comparand isn't also a :class:`date` object. - However, ``NotImplemented`` is returned instead if the other comparand has a + date2.toordinal()``. Date comparison raises :exc:`TypeError` if + the other comparand isn't also a :class:`date` object. However, + ``NotImplemented`` is returned instead if the other comparand has a :meth:`timetuple` attribute. This hook gives other kinds of date objects a chance at implementing mixed-type comparison. If not, when a :class:`date` object is compared to an object of a different type, :exc:`TypeError` is raised