pdb frames accessible after the termination occurs on uncaught exception

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

Línea de trabajo

The issue concerns Python's pdb behavior in the Library (Lib) component after an uncaught exception. Start by reproducing whether pdb frames remain accessible after termination, then identify the relevant library entry point and tests. Done means the post-termination frame behavior matches the intended exception-handling lifecycle and is covered by a regression test.

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

Descripción

stdlib type-bug
BPO 17026
Nosy @birkenfeld, @xdegaye

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 2013-01-24.17:18:33.322>
labels = ['type-bug', 'library']
title = 'pdb frames accessible after the termination occurs on uncaught exception'
updated_at = <Date 2019-04-26.19:47:53.423>
user = 'https://github.com/xdegaye'

bugs.python.org fields:

activity = <Date 2019-04-26.19:47:53.423>
actor = 'BreamoreBoy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2013-01-24.17:18:33.322>
creator = 'xdegaye'
dependencies = []
files = []
hgrepos = []
issue_num = 17026
keywords = []
message_count = 2.0
messages = ['180535', '223237']
nosy_count = 2.0
nosy_names = ['georg.brandl', 'xdegaye']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue17026'
versions = ['Python 2.7', '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.