[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 <report at bugs.python.org>
<http://bugs.python.org/issue17151>
_______________________________________