Occasionally check for Ctrl-C in long-running operations like sum

Abierto
#70,539 16 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
python

Línea de trabajo

Start by reviewing KeyboardInterrupt.patch and test_sig_int_builtins.py, the files attached to this issue. Check how the proposed tests exercise Ctrl-C during long-running built-in operations such as sum. Done means the relevant built-ins can be interrupted and the regression tests pass.

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

Descripción

3.7 (EOL) interpreter-core type-bug
BPO 26351
Nosy @rhettinger, @terryjreedy, @ncoghlan, @vstinner, @stevendaprano, @wimglenn, @treyhunner
Files
  • KeyboardInterrupt.patch: Allows interruption of builtin routines using ctrl-c
  • test_sig_int_builtins.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-02-12.17:47:32.154>
    labels = ['interpreter-core', 'type-bug', '3.7']
    title = 'Occasionally check for Ctrl-C in long-running operations like sum'
    updated_at = <Date 2016-09-30.14:54:40.369>
    user = 'https://github.com/stevendaprano'
    

    bugs.python.org fields:

    activity = <Date 2016-09-30.14:54:40.369>
    actor = 'trey'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Interpreter Core']
    creation = <Date 2016-02-12.17:47:32.154>
    creator = 'steven.daprano'
    dependencies = []
    files = ['44746', '44747']
    hgrepos = []
    issue_num = 26351
    keywords = ['patch']
    message_count = 15.0
    messages = ['260189', '260238', '260535', '260536', '260556', '276995', '276996', '277002', '277094', '277096', '277098', '277185', '277190', '277220', '277757']
    nosy_count = 8.0
    nosy_names = ['rhettinger', 'terry.reedy', 'ncoghlan', 'vstinner', 'steven.daprano', 'wim.glenn', 'gslavin', 'trey']
    pr_nums = []
    priority = 'low'
    resolution = None
    stage = None
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue26351'
    versions = ['Python 3.7']
    

    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.