Coroutines & async generators disagree on the iteration protocol semantics
Open
Nobody has claimed this yet.
3.10
3.11
interpreter-core
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 45088 |
|---|---|
| Nosy | @gvanrossum, @ambv, @1st1, @pablogsal |
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-09-02.20:32:30.403>
labels = ['interpreter-core', 'type-bug', '3.10', '3.11']
title = 'Coroutines & async generators disagree on the iteration protocol semantics'
updated_at = <Date 2021-09-03.03:26:08.506>
user = 'https://github.com/1st1'
bugs.python.org fields:
activity = <Date 2021-09-03.03:26:08.506>
actor = 'yselivanov'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2021-09-02.20:32:30.403>
creator = 'yselivanov'
dependencies = []
files = []
hgrepos = []
issue_num = 45088
keywords = []
message_count = 1.0
messages = ['400951']
nosy_count = 4.0
nosy_names = ['gvanrossum', 'lukasz.langa', 'yselivanov', 'pablogsal']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue45088'
versions = ['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 files or tests are identified in the issue; start by reading the migrated BPO issue 45088 and the linked discussion about coroutine and async-generator iteration semantics. A complete change would need an agreed protocol behavior and corresponding implementation and regression coverage, but the issue does not specify the target behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100