Use select.poll instead of select.select in SocketServer.BaseServer.serve_forever
Open
Nobody has claimed this yet.
3.13
performance
stdlib
topic-socket
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 31610 |
|---|---|
| Nosy | @vstinner, @giampaolo |
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-09-27.11:24:44.981>
labels = ['library', 'performance']
title = 'Use select.poll instead of select.select in SocketServer.BaseServer.serve_forever'
updated_at = <Date 2017-09-28.15:05:48.447>
user = 'https://bugs.python.org/bboneva'
bugs.python.org fields:
activity = <Date 2017-09-28.15:05:48.447>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-09-27.11:24:44.981>
creator = 'bboneva'
dependencies = []
files = []
hgrepos = []
issue_num = 31610
keywords = []
message_count = 4.0
messages = ['303127', '303247', '303251', '303254']
nosy_count = 3.0
nosy_names = ['vstinner', 'giampaolo.rodola', 'bboneva']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'performance'
url = 'https://bugs.python.org/issue31610'
versions = []
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 locating SocketServer.BaseServer.serve_forever in the Python standard-library sources and inspect how its current select.select call is used. Check the existing library tests for server behavior, then verify that the event loop uses select.poll while preserving its current serving behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100