no error when `abstractmethod` and `property` decorators are used in the wrong order
Open
Nobody has claimed this yet.
bug
topic-descriptors
topic-runtime-semantics
- Dominant language
- Python
- Stars
- 20.6k
- Forks
- 3.3k
- PR merge metrics
- PR metrics pending
Description
from abc import ABC, abstractmethod
class Foo(ABC):
@abstractmethod
@property
def foo(self) -> int:
...
this causes a runtime error, see https://github.com/python/cpython/issues/60471
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 playground example and compare mypy's behavior with the runtime failure described in the linked CPython issue. Trace how decorator combinations are analyzed, then add coverage for this snippet and verify that the incorrect order produces an appropriate diagnostic.
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