no error when setting property defined without decorator to incorrect type
Open
Nobody has claimed this yet.
feature
topic-descriptors
- Dominant language
- Python
- Stars
- 20.6k
- Forks
- 3.3k
- PR merge metrics
- PR metrics pending
Description
class A:
def _get_foo(self) -> int:
...
def _set_foo(self, value: int) -> None:
...
foo = property(fget=_get_foo, fset=_set_foo)
a = A()
a.foo = "" # no error
playground
related: #13127
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 property example and its mypy-play reproduction, then compare the behavior with related issue #13127. Trace how mypy infers the setter type for a property created without a decorator. Done means the shown assignment to a property whose setter expects int is reported as a type error, with appropriate regression coverage.
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
- 35/100