IDLE Debugger should handle interrupts

Abierto
#58,319 11 comentarios 0 reacciones 1 asignado Ver en GitHub

@terryjreedy ya está trabajando en esto.

Desde el 25/5/2017.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

OS-windows topic-IDLE type-bug
BPO 14111
Nosy @terryjreedy, @roseman, @mlouielu
PRs
  • python/cpython#1821
    		•
    Files
  • debug-running-or-stopped.py: Trivial cpu-intensive loop
  • Issue14111.patch
  • 0001-WIP.patch
    		•

    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 = 'https://github.com/terryjreedy'
closed_at = None
created_at = <Date 2012-02-24.19:47:19.101>
labels = ['expert-IDLE', 'type-bug', '3.10', 'OS-windows']
title = 'IDLE Debugger should handle interrupts'
updated_at = <Date 2020-12-04.22:09:27.281>
user = 'https://bugs.python.org/ltaylor934'

    bugs.python.org fields:

    activity = <Date 2020-12-04.22:09:27.281>
actor = 'markroseman'
assignee = 'terry.reedy'
closed = False
closed_date = None
closer = None
components = ['IDLE', 'Windows']
creation = <Date 2012-02-24.19:47:19.101>
creator = 'ltaylor934'
dependencies = []
files = ['24631', '24656', '46893']
hgrepos = []
issue_num = 14111
keywords = ['patch']
message_count = 11.0
messages = ['154150', '154433', '265100', '265103', '294330', '294338', '294447', '294483', '294530', '382320', '382537']
nosy_count = 4.0
nosy_names = ['terry.reedy', 'markroseman', 'ltaylor934', 'louielu']
pr_nums = ['1821']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue14111'
versions = ['Python 3.10']

    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.