bpo-29986: Doc: Delete tip to raise TypeError from tp_richcompare. (GH-16095)
(cherry picked from commit 375a3e2bdb
)
Co-authored-by: Julien Palard <julien@palard.fr>
This commit is contained in:
parent
60d5e2c5a5
commit
4556b1d35c
|
@ -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`:
|
||||
|
||||
|
|
Loading…
Reference in New Issue