python / python/mypy

(🐞) `Protocol` compatibility is broken for `__call__(self, *args: Any)`

Open
#16,568 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
20.6k
Forks
3.3k
PR merge metrics
PR metrics pending

Description

# mypy: disable-error-code=empty-body
from __future__ import annotations

from typing import Any, Protocol

class A(Protocol):
    def __call__(self, *args: Any) -> None: ...

class B1(A):
    def __call__(self, x: int) -> None: ...  # no error

class B2:
    def __call__(self, x: int) -> None: ...

a: A = B2()  # Incompatible types in assignment (expression has type "B2", variable has type "A")  [assignment]

@ilevkivskyi

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the provided Python reproducer through mypy and compare the Protocol-based A/B1 case with the structural B2 assignment. Trace the callable Protocol compatibility check that produces the assignment diagnostic. Done means B2 is accepted as an A while the existing incompatible cases remain correctly rejected.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.