From 4d6e8fe5d13a313314550d7ebffafaf62dea1df2 Mon Sep 17 00:00:00 2001
From: Raymond Hettinger <python@rcn.com>
Date: Wed, 16 Jul 2003 19:40:23 +0000
Subject: Clarify the lack of relationship between rich comparison operators.

Prompted by a discussion on comp.lang.python.
---
 Doc/ref/ref3.tex | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/Doc/ref/ref3.tex b/Doc/ref/ref3.tex
index 785a995..68d87b4 100644
--- a/Doc/ref/ref3.tex
+++ b/Doc/ref/ref3.tex
@@ -1089,6 +1089,11 @@ used in a Boolean context, the return value should be interpretable as
 a Boolean value, else a \exception{TypeError} will be raised.
 By convention, \code{False} is used for false and \code{True} for true.
 
+There are no implied relationships among the comparison operators.
+The truth of {\var{x}==\var{y}} does not imply that \code{\var{x}!=\var{y}}
+is false.  Accordingly, when defining \method{__eq__}, one should also
+define \method{__ne__} so that the operators will behave as expected.
+
 There are no reflected (swapped-argument) versions of these methods
 (to be used when the left argument does not support the operation but
 the right argument does); rather, \method{__lt__()} and
-- 
cgit v0.12

