Signatures of "__ior__" and "__or__" are incompatible when assigning __or__ with compatible method

Bug Report

Dear mypy team,

I was implementing arithmetic operations on a custom class and ran into the following issue:
When I don't define __or__ in the class body, but assign it with a function with a compatible type, mypy complains about incompatible signatures of __ior__ and __or__. (This is also true for other arithmetic dunders, see example).

I wanted to only allow inplace operations on that class and throw a common error on non-inplace operations.

To Reproduce

# this works and does not throw an error
class A:

    def __or__(self, v: int) -> A:...

    def __ior__(self, v: int) -> None: ...

    reveal_type(__or__)  # note: Revealed type is "def (_error.A, builtins.int) -> _error.A"
    reveal_type(__ior__)  # note: Revealed type is "def (_error.A, builtins.int)"


# this errors
class B:

    def _no(self, v: int) -> B: ...

    __or__ = _no

    def __ior__(self, v: int) -> None: ...  # error: Signatures of "__ior__" and "__or__" are incompatible

    reveal_type(__or__)  # note: Revealed type is "def (self: _error.B, v: builtins.int) -> _error.B"
    reveal_type(__ior__)  # note: Revealed type is "def (_error.B, builtins.int)"

NOTE: the same is true for __and__, __xor__, __add__, __sub__, __mul__, __truediv__, __floordiv__. (I haven't tested others.

Your Environment

• Mypy version used: 0.931
• Python version used: python3.9

Inizia riproducendo la differenza segnalata tra la definizione di or nella classe A e l’assegnazione di or da _no nella classe B, usando l’esempio Python 3.9 e il comportamento di mypy 0.931. Traccia il percorso del controllo dei tipi che confronta le firme di ior e or, quindi verifica il risultato con gli altri metodi dunder aritmetici elencati nel report. Il lavoro è completato quando i metodi assegnati compatibili non producono più erroneamente l’errore di incompatibilità, mentre le firme realmente incompatibili continuano a produrlo.