Handling Ctrl+C while waiting on I/O in Windows
Open
Nobody has claimed this yet.
3.10
3.8 (EOL)
3.9 (EOL)
interpreter-core
OS-windows
topic-IO
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 43523 |
|---|---|
| Nosy | @pfmoore, @tjguk, @zware, @eryksun, @zooba, @sovetov |
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 2021-03-16.21:48:50.125>
labels = ['interpreter-core', '3.8', '3.9', 'expert-IO', 'type-feature', '3.10', 'OS-windows']
title = 'Handling Ctrl+C while waiting on I/O in Windows'
updated_at = <Date 2021-03-16.23:52:56.038>
user = 'https://github.com/sovetov'
bugs.python.org fields:
activity = <Date 2021-03-16.23:52:56.038>
actor = 'eryksun'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core', 'Windows', 'IO']
creation = <Date 2021-03-16.21:48:50.125>
creator = 'sovetov'
dependencies = []
files = []
hgrepos = []
issue_num = 43523
keywords = []
message_count = 2.0
messages = ['388890', '388896']
nosy_count = 6.0
nosy_names = ['paul.moore', 'tim.golden', 'zach.ware', 'eryksun', 'steve.dower', 'sovetov']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue43523'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']
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 reviewing the linked BPO issue 43523 and its two messages, then investigate how CPython's interpreter core handles Windows I/O waits and Ctrl+C. The issue does not name files, tests, or a precise expected behavior; done would require an agreed interruption behavior and corresponding implementation and tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100