SIGINT blocked by socket operations like recv on Windows
Open
Nobody has claimed this yet.
3.8 (EOL)
OS-windows
topic-socket
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 41437 |
|---|---|
| Nosy | @pfmoore, @tjguk, @zware, @eryksun, @zooba, @zmwangx |
| Files |
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 2020-07-29.18:13:12.163>
labels = ['type-bug', '3.8', 'OS-windows']
title = 'SIGINT blocked by socket operations like recv on Windows'
updated_at = <Date 2020-07-29.22:20:55.859>
user = 'https://github.com/zmwangx'
bugs.python.org fields:
activity = <Date 2020-07-29.22:20:55.859>
actor = 'eryksun'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Windows']
creation = <Date 2020-07-29.18:13:12.163>
creator = 'zmwangx'
dependencies = []
files = ['49348']
hgrepos = []
issue_num = 41437
keywords = []
message_count = 2.0
messages = ['374580', '374590']
nosy_count = 6.0
nosy_names = ['paul.moore', 'tim.golden', 'zach.ware', 'eryksun', 'steve.dower', 'zmwangx']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue41437'
versions = ['Python 3.8']
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 running the attached socket_sigint_sigbreak.py reproducer on Windows and confirming the SIGINT behavior during recv. Then trace the relevant Python socket and signal-handling entry points; done means the reproducer no longer leaves SIGINT blocked by the socket operation, with regression coverage for the reported case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100