[New-bugs-announce] [issue17151] Python 3 changement of behavior with __ne__: documentation not updated
report at bugs.python.org
Thu Feb 7 16:34:19 CET 2013
New submission from Franck Michea:
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 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.
assignee: docs at python
nosy: docs at python, kushou
title: Python 3 changement of behavior with __ne__: documentation not updated
versions: Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5
Python tracker <report at bugs.python.org>
More information about the New-bugs-announce