KeyboardInterrupt while in input() not catchable on Windows 10
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- operating-systems
Research direction
Start by running the uploaded keyint_poc.py and ccbug.py proof-of-concept files on Windows 10 to reproduce the uncaught KeyboardInterrupt during input(). Then trace the CPython input handling involved and verify that the interrupt becomes catchable without regressing the reported Python versions.
Written by the indexing model from the issue text.
Description
| BPO | 26531 |
|---|---|
| Nosy | @pfmoore, @vstinner, @tjguk, @vadmium, @zware, @zooba |
| 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 2016-03-10.16:18:45.880>
labels = ['type-bug', 'OS-windows']
title = 'KeyboardInterrupt while in input() not catchable on Windows 10'
updated_at = <Date 2016-03-11.16:14:12.441>
user = 'https://bugs.python.org/jecanne'
bugs.python.org fields:
activity = <Date 2016-03-11.16:14:12.441>
actor = 'jecanne'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Windows']
creation = <Date 2016-03-10.16:18:45.880>
creator = 'jecanne'
dependencies = []
files = ['42117', '42120']
hgrepos = []
issue_num = 26531
keywords = []
message_count = 9.0
messages = ['261508', '261509', '261511', '261512', '261513', '261515', '261520', '261523', '261578']
nosy_count = 8.0
nosy_names = ['paul.moore', 'vstinner', 'tim.golden', 'martin.panter', 'zach.ware', 'steve.dower', 'tjguk', 'jecanne']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue26531'
versions = ['Python 2.7', 'Python 3.5', 'Python 3.6']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
🐛 Bug 🔔 Pending processing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
jumpserver/jumpserver#17584 ·