From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Date: Wed, 3 Nov 2021 09:30:59 +0000 (-0700) Subject: bpo-45633: Fix newtypes doc typo (GH-29318) (GH-29365) X-Git-Tag: v3.9.8~12 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=3a93c669f50f090a227e964eb26ce8a3d1dc1202;p=thirdparty%2FPython%2Fcpython.git bpo-45633: Fix newtypes doc typo (GH-29318) (GH-29365) (cherry picked from commit 454cdb99abcda37413b15167cda564091fec2572) Co-authored-by: Dmitry Smirnov --- diff --git a/Doc/extending/newtypes.rst b/Doc/extending/newtypes.rst index 638b00a4c0f6..7c51d8e29cd4 100644 --- a/Doc/extending/newtypes.rst +++ b/Doc/extending/newtypes.rst @@ -388,7 +388,7 @@ analogous to the :ref:`rich comparison methods `, like :c:func:`PyObject_RichCompareBool`. This function is called with two Python objects and the operator as arguments, -where the operator is one of ``Py_EQ``, ``Py_NE``, ``Py_LE``, ``Py_GT``, +where the operator is one of ``Py_EQ``, ``Py_NE``, ``Py_LE``, ``Py_GE``, ``Py_LT`` or ``Py_GT``. It should compare the two objects with respect to the specified operator and return ``Py_True`` or ``Py_False`` if the comparison is successful, ``Py_NotImplemented`` to indicate that comparison is not