`concurrent.futures.Future.set_running_or_notify_cancel` does not notify cancel

Abierto
#66,820 4 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
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
python
Área
backend

Línea de trabajo

Start at concurrent.futures.Future.set_running_or_notify_cancel and compare its cancellation behavior with change-callbacks.patch, change-docs.patch, change-docs-and-waiters.patch, and non-magic-waiters.patch. Determine which documented behavior should apply consistently to callbacks and waiters, then verify the relevant library behavior and documentation.

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

Descripción

docs stdlib topic-multiprocessing
BPO 22630
Nosy @brianquinlan, @pitrou
Files
  • change-callbacks.patch: Patch to change callbacks to match docs
  • change-docs.patch: Fixes the documentation to match the current behaviour.
  • change-docs-and-waiters.patch: in addition to fixing the documentation, this also fixes the inconsistency between waiters and callbacks by invoking waiters' add_cancelled method in cancel.
  • non-magic-waiters.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 2014-10-14.09:05:54.451>
labels = ['library', 'docs']
title = '`concurrent.futures.Future.set_running_or_notify_cancel` does not notify cancel'
updated_at = <Date 2019-05-07.16:26:55.520>
user = 'https://bugs.python.org/bwhmather'

    bugs.python.org fields:

    activity = <Date 2019-05-07.16:26:55.520>
actor = 'bquinlan'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'Library (Lib)']
creation = <Date 2014-10-14.09:05:54.451>
creator = 'bwhmather'
dependencies = []
files = ['36908', '36909', '36910', '37017']
hgrepos = []
issue_num = 22630
keywords = ['patch']
message_count = 4.0
messages = ['229282', '230017', '303588', '341775']
nosy_count = 4.0
nosy_names = ['bquinlan', 'pitrou', 'docs@python', 'bwhmather']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue22630'
versions = ['Python 3.2', 'Python 3.3', '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.