[issue17151] Python 3 changement of behavior with __ne__: documentation not updated

[Franck Michea]

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[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__

--
assignee: docs@python
components: Documentation
messages: 181620
nosy: docs@python, kushou
priority: normal
severity: normal
status: open
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 rep...@bugs.python.org
http://bugs.python.org/issue17151
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue17151] Python 3 changement of behavior with __ne__: documentation not updated

[Mark Dickinson]

Mark Dickinson added the comment:

There's a (long-standing) issue already open for this: #4395.  I'll close this 
as a duplicate and add a note to that issue;  with any luck, pinging that issue 
might produce some movement.

--
nosy: +mark.dickinson
resolution:  - duplicate
status: open - closed
superseder:  - Document auto __ne__ generation; provide a use case for 
non-trivial __ne__

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17151
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com