Preserve AttributeError exception context in __getattr__
Open
Nobody has claimed this yet.
3.9 (EOL)
interpreter-core
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 40519 |
|---|---|
| Nosy | @ammaraskar, @Arusekk, @pasenor |
| Files |
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 2020-05-05.14:32:40.592>
labels = ['interpreter-core', 'type-bug', '3.9']
title = 'Preserve AttributeError exception context in __getattr__'
updated_at = <Date 2020-05-05.14:36:34.734>
user = 'https://github.com/Arusekk'
bugs.python.org fields:
activity = <Date 2020-05-05.14:36:34.734>
actor = 'Arusekk'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2020-05-05.14:32:40.592>
creator = 'Arusekk'
dependencies = []
files = ['49122', '49123']
hgrepos = []
issue_num = 40519
keywords = ['patch']
message_count = 2.0
messages = ['368152', '368154']
nosy_count = 3.0
nosy_names = ['ammar2', 'Arusekk', 'pasenor']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue40519'
versions = ['Python 3.9']
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 by reviewing the attached typeobject.patch and robust.patch files, which contain the proposed approaches. Then locate the relevant CPython interpreter code and add or run focused tests for the AttributeError behavior; done means the exception context is preserved without breaking existing attribute lookup behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100