From 9609cea0449979a56049bbfe7251e98621acfb2b Mon Sep 17 00:00:00 2001 From: Georg Brandl Date: Tue, 9 Sep 2008 19:31:57 +0000 Subject: [PATCH] #3803: fix docs for comparison of unequal types. --- Doc/reference/expressions.rst | 17 +++++++---------- 1 file changed, 7 insertions(+), 10 deletions(-) diff --git a/Doc/reference/expressions.rst b/Doc/reference/expressions.rst index 945df61f16a..7931b950dd9 100644 --- a/Doc/reference/expressions.rst +++ b/Doc/reference/expressions.rst @@ -1003,16 +1003,13 @@ pretty). The operators ``<``, ``>``, ``==``, ``>=``, ``<=``, and ``!=`` compare the values of two objects. The objects need not have the same type. If both are -numbers, they are converted to a common type. Otherwise, objects of different -types *always* compare unequal, and are ordered consistently but arbitrarily. -You can control comparison behavior of objects of non-builtin types by defining -a :meth:`__cmp__` method or rich comparison methods like :meth:`__gt__`, -described in section :ref:`specialnames`. - -(This unusual definition of comparison was used to simplify the definition of -operations like sorting and the :keyword:`in` and :keyword:`not in` operators. -In the future, the comparison rules for objects of different types are likely to -change.) +numbers, they are converted to a common type. Otherwise, the ``==`` and ``!=`` +operators *always* consider objects of different types to be unequal, while the +``<``, ``>``, ``>=`` and ``<=`` operators raise a :exc:`TypeError` when +comparing objects of different types that do not implement these operators for +the given pair of types. You can control comparison behavior of objects of +non-builtin types by defining rich comparison methods like :meth:`__gt__`, +described in section :ref:`customization`. Comparison of objects of the same type depends on the type: