AttributeError from @property inadvertantly flows into __getattr__
Open
Nobody has claimed this yet.
3.10
3.11
3.9 (EOL)
interpreter-core
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 45985 |
|---|---|
| Nosy | @AlexWaygood |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2021-12-05.11:02:26.538>
labels = ['type-bug', '3.9', '3.10', '3.11']
title = 'AttributeError from @property inadvertantly flows into __getattr__'
updated_at = <Date 2021-12-12.19:45:16.374>
user = 'https://bugs.python.org/koreno'
bugs.python.org fields:
activity = <Date 2021-12-12.19:45:16.374>
actor = 'AlexWaygood'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2021-12-05.11:02:26.538>
creator = 'koreno'
dependencies = []
files = []
hgrepos = []
issue_num = 45985
keywords = []
message_count = 1.0
messages = ['407701']
nosy_count = 2.0
nosy_names = ['AlexWaygood', 'koreno']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue45985'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
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
No source file, test, reproducer, or entry point is named in the issue. Start with the linked BPO issue 45985 and trace the reported behavior through the relevant CPython attribute-lookup implementation and tests. Done means the intended interaction is established and covered by a focused regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100