(📚) docs for PLW1641 known problems doesn't make sense

[KotlinIsland]

# Known problems
Does not check for `__hash__` implementations in superclasses.

__hash__ defined in a superclass doesn't affect the semantics:

class A:
    def __hash__(self):
        return 1

class B(A):
   def __eq__(self, other):
       return False
B.__hash__ # None

[zanieb]

The rule is

Checks for classes that implement __eq__ but not __hash__.

So.. if you have this:

class A:
    def __hash__(self):
        return 1

class B(A):
   def __eq__(self, other):
       return False

B implements __hash__ via A but is not detected by Ruff.

What doesn't make sense about this?

[KotlinIsland]

What doesn't make sense about this?

as in my OP:

print(B.__hash__) # None

[KotlinIsland]

A class that overrides eq() and does not define hash() will have its hash() implicitly set to None.

source: https://docs.python.org/3/reference/datamodel.html#object.__hash__

[charliermarsh]

Wow, so it's just when __eq__ is defined?

[zanieb]

@KotlinIsland sorry your OP doesn't have inheritance

Interesting find though!

[KotlinIsland]

sorry your OP doesn't have inheritance

fail...

i've updated it