KeyboardInterrupt while in input() not catchable on Windows 10

Open
#70,718 9 comments 0 reactions 0 assignees View on GitHub

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

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

OS-windows type-bug
BPO 26531
Nosy @pfmoore, @vstinner, @tjguk, @vadmium, @zware, @zooba
Files
  • keyint_poc.py: Proof of Concept
  • ccbug.py
  • 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

    Open the contributing guide

    First steps

    1. Read the whole issue, then the project's contributing guide.
    2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
    3. Fork the repository and make your change on a branch.
    4. Open a pull request that references the issue number.

    More from python/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.