R. David Murray added the comment:
This has already been fixed, and the change is visible in the online
documentation.
--
nosy: +r.david.murray
resolution: -> duplicate
stage: -> committed/rejected
status: open -> closed
superseder: -> confusing docs with regard to __hash__
New submission from Max:
In dev/reference/datamodel#object.__hash__, there are two paragraphs that seem
inconsistent. The first paragraph seems to say that a class that overrides
__eq__() *should* explicitly flag itself as unhashable. The next paragraph says
that a class that overrides __eq__(
