No equivalent of `inspect.getcoroutinestate` for PyAsyncGenASend instances
Open
Nobody has claimed this yet.
3.11
3.12
3.13
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 37771 |
|---|---|
| Nosy | @agronholm, @1st1, @graingert, @GeeTransit |
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-08-06.01:20:30.940>
labels = ['type-bug', '3.8', '3.9']
title = 'No equivalent of `inspect.getcoroutinestate` for PyAsyncGenASend instances'
updated_at = <Date 2021-03-06.17:47:09.352>
user = 'https://github.com/GeeTransit'
bugs.python.org fields:
activity = <Date 2021-03-06.17:47:09.352>
actor = 'graingert'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Demos and Tools']
creation = <Date 2019-08-06.01:20:30.940>
creator = 'GeeTransit'
dependencies = []
files = []
hgrepos = []
issue_num = 37771
keywords = []
message_count = 1.0
messages = ['349093']
nosy_count = 4.0
nosy_names = ['alex.gronholm', 'yselivanov', 'graingert', 'GeeTransit']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue37771'
versions = ['Python 3.8', '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
The issue names inspect.getcoroutinestate and PyAsyncGenASend instances but does not identify files or tests. Start by locating the existing coroutine-state API and the async-generator send implementation, then determine what state information an equivalent should expose. Done means the behavior is implemented and covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100