From 4556b1d35c352c975f3cf066362cb6e24efe0668 Mon Sep 17 00:00:00 2001 From: "Miss Islington (bot)" <31488909+miss-islington@users.noreply.github.com> Date: Fri, 13 Sep 2019 06:14:42 -0700 Subject: [PATCH] bpo-29986: Doc: Delete tip to raise TypeError from tp_richcompare. (GH-16095) (cherry picked from commit 375a3e2bdbeb4dce69aba4b5bc90f55fe27e81b4) Co-authored-by: Julien Palard --- Doc/c-api/typeobj.rst | 6 ------ 1 file changed, 6 deletions(-) diff --git a/Doc/c-api/typeobj.rst b/Doc/c-api/typeobj.rst index f8e30a0380b..7c7a79129cc 100644 --- a/Doc/c-api/typeobj.rst +++ b/Doc/c-api/typeobj.rst @@ -1311,12 +1311,6 @@ and :c:type:`PyType_Type` effectively act as defaults.) ``Py_NotImplemented``, if another error occurred it must return *NULL* and set an exception condition. - .. note:: - - If you want to implement a type for which only a limited set of - comparisons makes sense (e.g. ``==`` and ``!=``, but not ``<`` and - friends), directly raise :exc:`TypeError` in the rich comparison function. - The following constants are defined to be used as the third argument for :c:member:`~PyTypeObject.tp_richcompare` and for :c:func:`PyObject_RichCompare`: