Author franck
Recipients docs@python, franck
Date 2013-02-07.15:34:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1360251259.3.0.329716783607.issue17151@psf.upfronthosting.co.za>
In-reply-to
Content
Hi. As of python 3, behavior of object.__ne__ changed to call (not object.__eq__) if implemented. This changement can be seen in function object_richcompare in file Objects/typeobject.c.

Documentation didn't change though, still saying[1] that "There are no implied relationships among the comparison operators. [...] Accordingly, when defining __eq__(), one should also define __ne__()".

Maybe a paragraph about this new behavior would be fine? I am not sure if last sentence of last paragraph is what it means, but it was already there in python 2 doc so guess no. I am not sure about how to write it so no patch, sorry.

[1] http://docs.python.org/3.3/reference/datamodel.html#object.__eq__
History
Date User Action Args
2013-02-07 15:34:19francksetrecipients: + franck, docs@python
2013-02-07 15:34:19francksetmessageid: <1360251259.3.0.329716783607.issue17151@psf.upfronthosting.co.za>
2013-02-07 15:34:19francklinkissue17151 messages
2013-02-07 15:34:18franckcreate