[issue41400] Remove references to nonexisting __ne__ methods

Facundo Batista added the comment: >From a "consumer" POV, it's totally useful to see that `__ne__` is part of >what Set (and others) provides, even if it's implemented in the Set class >itself or wherever. So +1 to leave it like it's currently is. -- nosy: +facundobatista

[issue41400] Remove references to nonexisting __ne__ methods

Raymond Hettinger added the comment: >From a user point of view, your edit makes it look like they have to supply >__ne__() if they want support for the != operator. The user would have to >know the subtle details of the language to know this is not the case. In >documentation, more so tha

[issue41400] Remove references to nonexisting __ne__ methods

Serhiy Storchaka added the comment: Is it good to provide incorrect information in the documentation? It is a matter of correctness, not style. -- ___ Python tracker ___

[issue41400] Remove references to nonexisting __ne__ methods

Raymond Hettinger added the comment: s/pedantic/formally but not helpfully/ -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue41400] Remove references to nonexisting __ne__ methods

Raymond Hettinger added the comment: This will make the docs confusing and create an uncertainty for a user: if they define __eq__, do they, can they, or should they define __ne__. Also, it feels weird to have lists of five rich comparison methods rather than all six. Tthe current docs be

[issue41400] Remove references to nonexisting __ne__ methods

Change by Serhiy Storchaka : -- keywords: +patch pull_requests: +20769 stage: -> patch review pull_request: https://github.com/python/cpython/pull/21628 ___ Python tracker ___

[issue41400] Remove references to nonexisting __ne__ methods

New submission from Serhiy Storchaka : There is the documentation for method __ne__ implementations in classes Set, Mapping, Header, Charset, Binary, but all these implementations are removed now and the default implementation of object.__ne__ is used instead. -- assignee: docs@python