unittest ignores the first ctrl-c when it shouldn't

Open
#70,088 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
testing-qa

Research direction

Start by reviewing the attached dont-ignore-first-ctrl-c.patch and dont-ignore-first-ctrl-c-with-tests.patch files, then reproduce the unittest Ctrl-C behavior. Done means the first Ctrl-C is no longer ignored and the regression is covered by tests.

Written by the indexing model from the issue text.

Description

stdlib type-bug
BPO 25900
Nosy @mgedmin, @rbtcollins, @voidspace
Files
  • dont-ignore-first-ctrl-c.patch
  • dont-ignore-first-ctrl-c-with-tests.patch: v2
    		•

    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 2015-12-18.08:48:29.595>
labels = ['type-bug', 'library']
title = "unittest ignores the first ctrl-c when it shouldn't"
updated_at = <Date 2016-03-14.01:27:23.177>
user = 'https://github.com/mgedmin'

    bugs.python.org fields:

    activity = <Date 2016-03-14.01:27:23.177>
actor = 'rbcollins'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2015-12-18.08:48:29.595>
creator = 'mgedmin'
dependencies = []
files = ['41345', '41383']
hgrepos = []
issue_num = 25900
keywords = ['patch']
message_count = 6.0
messages = ['256656', '256800', '256830', '256832', '256833', '261706']
nosy_count = 3.0
nosy_names = ['mgedmin', 'rbcollins', 'michael.foord']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue25900'
versions = []

    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.