asyncio: selector_events: add_urgent() for urgent data to read, 3rd argument of select.select()
Open
Nobody has claimed this yet.
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 30847 |
|---|---|
| Nosy | @gvanrossum, @vstinner, @1st1, @pklanke |
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-07-04.13:51:23.279>
labels = ['type-feature', '3.7', 'expert-asyncio']
title = 'asyncio: selector_events: add_urgent() for urgent data to read, 3rd argument of select.select()'
updated_at = <Date 2017-07-06.11:22:47.102>
user = 'https://github.com/pklanke'
bugs.python.org fields:
activity = <Date 2017-07-06.11:22:47.102>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['asyncio']
creation = <Date 2017-07-04.13:51:23.279>
creator = 'pklanke'
dependencies = []
files = []
hgrepos = []
issue_num = 30847
keywords = []
message_count = 9.0
messages = ['297652', '297653', '297654', '297655', '297722', '297765', '297809', '297821', '297823']
nosy_count = 4.0
nosy_names = ['gvanrossum', 'vstinner', 'yselivanov', 'pklanke']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue30847'
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
Start by reading asyncio's selector_events implementation and the select.select() interface, focusing on the third argument for urgent data. Determine how an add_urgent() API should integrate with the existing event loop, then verify that urgent data is detected and exposed without regressing ordinary reads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100