Clearing stack frame of suspended coroutine causes coroutine to malfunction
Open
Nobody has claimed this yet.
interpreter-core
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 42566 |
|---|---|
| Nosy | @zerotypic |
| 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-12-04.08:46:49.162>
labels = ['interpreter-core', 'type-bug']
title = 'Clearing stack frame of suspended coroutine causes coroutine to malfunction'
updated_at = <Date 2020-12-04.08:46:49.162>
user = 'https://github.com/zerotypic'
bugs.python.org fields:
activity = <Date 2020-12-04.08:46:49.162>
actor = 'zerotypic'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2020-12-04.08:46:49.162>
creator = 'zerotypic'
dependencies = []
files = ['49654']
hgrepos = []
issue_num = 42566
keywords = []
message_count = 1.0
messages = ['382472']
nosy_count = 1.0
nosy_names = ['zerotypic']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue42566'
versions = ['Python 3.6']
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 attached async_bug.py reproducer and run it against the current CPython build to observe the suspended-coroutine failure. Trace the interpreter-core handling of cleared coroutine stack frames, then add a regression test demonstrating the expected behavior and verify that the reproducer no longer malfunctions.
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
- 30/100