signal handler never gets called

Abierto
#49,565 9 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

Línea de trabajo

Start by running tsig.py, the script attached to the issue, to reproduce the signal behavior. Then read select_select.diff and the issue history to understand the proposed context; no current test or acceptance criterion is named, so confirm the expected behavior with maintainers before changing code.

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

Descripción

docs interpreter-core stdlib type-bug
BPO 5315
Nosy @tim-one, @birkenfeld, @terryjreedy, @pitrou, @vstinner, @ssbr
Files
  • tsig.py: Python script which triggers the strange behavior
  • select_select.diff
  • 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 2009-02-19.13:47:06.207>
    labels = ['interpreter-core', 'type-bug', 'library', 'docs']
    title = 'signal handler never gets called'
    updated_at = <Date 2018-03-29.20:05:00.027>
    user = 'https://bugs.python.org/pts'
    

    bugs.python.org fields:

    activity = <Date 2018-03-29.20:05:00.027>
    actor = 'Patrick Fink'
    assignee = 'docs@python'
    closed = False
    closed_date = None
    closer = None
    components = ['Documentation', 'Interpreter Core', 'Library (Lib)']
    creation = <Date 2009-02-19.13:47:06.207>
    creator = 'pts'
    dependencies = []
    files = ['13138', '39489']
    hgrepos = []
    issue_num = 5315
    keywords = ['patch']
    message_count = 9.0
    messages = ['82472', '100306', '100309', '102829', '102850', '244015', '244019', '246963', '314669']
    nosy_count = 12.0
    nosy_names = ['tim.peters', 'georg.brandl', 'terry.reedy', 'pitrou', 'amcnabb', 'vstinner', 'Devin Jeanpierre', 'pts', 's7v7nislands', 'neologix', 'Netto', 'Patrick Fink']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = 'patch review'
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue5315'
    versions = ['Python 2.7', 'Python 3.4', 'Python 3.5', 'Python 3.6']
    

    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.