Pdb debugs itself after ^C and a breakpoint is set anywhere

Abierto
#58,993 3 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
30/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
python
Área
devtools

Línea de trabajo

Start by reviewing the linked pdb_default.patch and the pdb debugger entry points in the Python standard library. Reproduce the Ctrl-C case with a breakpoint set, then verify that pdb does not enter its own debugger; add or update focused regression coverage for the behavior.

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

Descripción

stdlib type-bug
BPO 14788
Nosy @birkenfeld, @blueyed, @xdegaye
Files
  • pdb_default.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 = None
closed_at = None
created_at = <Date 2012-05-12.10:07:36.784>
labels = ['type-bug', 'library']
title = 'Pdb debugs itself after ^C and a breakpoint is set anywhere'
updated_at = <Date 2019-04-19.10:51:51.502>
user = 'https://github.com/xdegaye'

    bugs.python.org fields:

    activity = <Date 2019-04-19.10:51:51.502>
actor = 'blueyed'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2012-05-12.10:07:36.784>
creator = 'xdegaye'
dependencies = []
files = ['25547']
hgrepos = []
issue_num = 14788
keywords = ['patch']
message_count = 3.0
messages = ['160467', '222267', '340536']
nosy_count = 3.0
nosy_names = ['georg.brandl', 'blueyed', 'xdegaye']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue14788'
versions = ['Python 3.4', 'Python 3.5']

    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.