Ability to join() threads in concurrent.futures.ThreadPoolExecutor
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 30/100
Línea de trabajo
Start by reading the concurrent.futures.ThreadPoolExecutor implementation and its existing shutdown behavior. The issue names no files or tests and does not define the join() API semantics, so first determine the intended behavior and how completion should be verified before proposing a change.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
| BPO | 22361 |
|---|---|
| Nosy | @brianquinlan, @MojoVampire |
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-09-08.10:29:45.590>
labels = ['type-feature', 'library']
title = 'Ability to join() threads in concurrent.futures.ThreadPoolExecutor'
updated_at = <Date 2019-05-06.19:52:27.697>
user = 'https://bugs.python.org/dktrkranz'
bugs.python.org fields:
activity = <Date 2019-05-06.19:52:27.697>
actor = 'bquinlan'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2014-09-08.10:29:45.590>
creator = 'dktrkranz'
dependencies = []
files = []
hgrepos = []
issue_num = 22361
keywords = []
message_count = 4.0
messages = ['226569', '226615', '226629', '341629']
nosy_count = 3.0
nosy_names = ['bquinlan', 'dktrkranz', 'josh.r']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue22361'
versions = ['Python 3.4']
- Lenguaje dominante
- Python
- Estrellas
- 77.2k
- Forks
- 36k
- Merge medio
- 1 d 9 h
- PR fusionados (30 d)
- 558
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de python/cpython
-
docs pending
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
stdlib type-feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
stdlib type-feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
build type-bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
-
stdlib topic-email type-feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100