(🐞) Invalid error when inplace operator is an instance, not 'function'
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 20.6k
- Forks
- 3.3k
- PR merge metrics
- PR metrics pending
Description
Based on testGenericOperatorMethodOverlapping
class B:
def __init__(self, _): ...
def __call__(self, x: object) -> object: ...
class A:
@B
def __or__(self) -> None: ...
def __ior__(self, x: object) -> object: ... # error: Signatures of "__ior__" and "__or__" are incompatible [misc]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the testGenericOperatorMethodOverlapping case mentioned in the report and trace how mypy checks the relationship between or and ior when or is decorated with an instance. Reproduce the example, then verify that the erroneous incompatible-signatures diagnostic is no longer emitted while valid operator checks remain covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100