signal.set_wakeup_fd() doesn't work if the signal don't have handler

Abierto
#69,668 12 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
28/100
Tipo de issue
Documentación
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
python
Área
documentation

Línea de trabajo

Start by reading the documentation for signal.set_wakeup_fd() and the historical discussion linked in the issue. Determine what behavior should be documented when a signal has no handler; done means the documentation clearly explains the expected behavior and any relevant limitation.

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

Descripción

docs
BPO 25482
Nosy @atsuoishimoto, @vstinner, @benjaminp

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 2015-10-26.11:34:56.021>
labels = ['docs']
title = "signal.set_wakeup_fd() doesn't work if the signal don't have handler"
updated_at = <Date 2015-10-30.11:39:35.835>
user = 'https://github.com/atsuoishimoto'

bugs.python.org fields:

activity = <Date 2015-10-30.11:39:35.835>
actor = 'ishimoto'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2015-10-26.11:34:56.021>
creator = 'ishimoto'
dependencies = []
files = []
hgrepos = []
issue_num = 25482
keywords = []
message_count = 12.0
messages = ['253468', '253517', '253520', '253602', '253657', '253677', '253711', '253712', '253724', '253727', '253728', '253729']
nosy_count = 4.0
nosy_names = ['ishimoto', 'vstinner', 'benjamin.peterson', 'docs@python']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue25482'
versions = ['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.