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

Abierto
#70,088 6 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
python
Área
testing-qa

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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 = []

    Lenguaje dominante
    Python
    Estrellas
    77.2k
    Forks
    36k
    Merge medio
    1 d 9 h
    PR fusionados (30 d)
    558

    Guía de contribución

    Abrir la guía de contribución

    Primeros pasos

    1. Lee el issue completo y luego la guía de contribución del proyecto.
    2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
    3. Haz un fork del repositorio y trabaja en una rama.
    4. Abre un pull request que haga referencia al número del issue.

    Más de python/cpython

    Todos los issues de python/cpython

    Issues similares

    Más issues de Python

    Recibe los nuevos issues en tu correo

    Un resumen breve de issues de GitHub para principiantes.