Improve reporting of broken stdout pipe during interpreter shutdown

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

Línea de trabajo

Start by reviewing python-sigint_and_epipe_straces.txt and flush_stdout_at_shutdown.patch, the historical evidence and proposed change attached to this issue. Determine the current interpreter-shutdown behavior for a broken stdout pipe and define improved reporting before validating the result with an appropriate regression test.

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

Descripción

topic-IO type-bug
BPO 11380
Nosy @terryjreedy, @ncoghlan, @pitrou, @rbtcollins, @florentx, @vadmium
Files
  • python-sigint_and_epipe_straces.txt: strace of issue in 3.2.2, 3.1.2, and 2.5.2
  • flush_stdout_at_shutdown.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 2011-03-03.01:32:45.546>
labels = ['type-bug', 'expert-IO']
title = 'Improve reporting of broken stdout pipe during interpreter shutdown'
updated_at = <Date 2018-06-16.10:13:08.003>
user = 'https://bugs.python.org/ulidtko'

    bugs.python.org fields:

    activity = <Date 2018-06-16.10:13:08.003>
actor = 'martin.panter'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['IO']
creation = <Date 2011-03-03.01:32:45.546>
creator = 'ulidtko'
dependencies = []
files = ['24517', '31853']
hgrepos = []
issue_num = 11380
keywords = ['patch']
message_count = 16.0
messages = ['129930', '130083', '153320', '198316', '198332', '198338', '198339', '198345', '198347', '198349', '213109', '248574', '248579', '248625', '248626', '319729']
nosy_count = 11.0
nosy_names = ['terry.reedy', 'ncoghlan', 'pitrou', 'rbcollins', 'zzzeek', 'flox', 'ulidtko', 'martin.panter', 'Jeremy.Fishman', 'daumiller', 'Christopher.Heiny']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue11380'
versions = ['Python 2.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.