Define a general "asynchronous operation introspection" protocol
Open
Nobody has claimed this yet.
3.7 (EOL)
interpreter-core
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 31230 |
|---|---|
| Nosy | @ncoghlan, @1st1, @syncosmic |
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 2017-08-18.02:25:30.237>
labels = ['type-feature', '3.7']
title = 'Define a general "asynchronous operation introspection" protocol'
updated_at = <Date 2017-08-19.16:47:44.039>
user = 'https://github.com/ncoghlan'
bugs.python.org fields:
activity = <Date 2017-08-19.16:47:44.039>
actor = 'yselivanov'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2017-08-18.02:25:30.237>
creator = 'ncoghlan'
dependencies = []
files = []
hgrepos = []
issue_num = 31230
keywords = []
message_count = 10.0
messages = ['300468', '300471', '300472', '300475', '300476', '300477', '300517', '300564', '300580', '300587']
nosy_count = 3.0
nosy_names = ['ncoghlan', 'yselivanov', 'syncosmic']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue31230'
versions = ['Python 3.7']
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 no files, tests, or entry points. Start by reading the migrated BPO issue 31230 and its discussion; use the Python 3.7 target and the requested asynchronous operation introspection protocol to establish scope and acceptance criteria before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100