calling super() causes __class__ to be not defined when sys.settrace(trace) is set
Open
Nobody has claimed this yet.
3.8 (EOL)
interpreter-core
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 36606 |
|---|---|
| Nosy | @ncoghlan, @nedbat, @benjaminp, @voidspace, @ericsnowcurrently, @tirkarthi |
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 2019-04-11.17:18:57.188>
labels = ['interpreter-core', 'type-bug', '3.8']
title = 'calling super() causes __class__ to be not defined when sys.settrace(trace) is set'
updated_at = <Date 2019-04-11.17:18:57.188>
user = 'https://github.com/tirkarthi'
bugs.python.org fields:
activity = <Date 2019-04-11.17:18:57.188>
actor = 'xtreak'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2019-04-11.17:18:57.188>
creator = 'xtreak'
dependencies = []
files = []
hgrepos = []
issue_num = 36606
keywords = []
message_count = 1.0
messages = ['339988']
nosy_count = 6.0
nosy_names = ['ncoghlan', 'nedbat', 'benjamin.peterson', 'michael.foord', 'eric.snow', 'xtreak']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue36606'
versions = ['Python 3.8']
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 files or tests are named. Start by reproducing the reported interaction between calling super(), class, and sys.settrace(trace), then trace it through the interpreter-core implementation. Done means the behavior is understood and corrected with a regression test, but the issue does not define the expected result in more detail.
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