From: Julien Palard <julien@palard.fr>
Date: Fri, 13 Sep 2019 13:07:37 +0000 (+0200)
Subject: bpo-29986: Doc: Delete tip to raise TypeError from tp_richcompare. (GH-16095)
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=375a3e2bdbeb4dce69aba4b5bc90f55fe27e81b4;p=python

bpo-29986: Doc: Delete tip to raise TypeError from tp_richcompare. (GH-16095)
---

diff --git a/Doc/c-api/typeobj.rst b/Doc/c-api/typeobj.rst
index f8e30a0380..7c7a79129c 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`: