Make ElementTree event handling more modular to allow custom targets for the non-blocking parser
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 20/100
Línea de trabajo
Start by reviewing the ElementTree non-blocking parser implementation and the linked PRs gh-156888 and gh-157439, since no source files or tests are named. The work is done when event handling is modular enough to support custom targets for the non-blocking parser.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
| BPO | 18902 |
|---|---|
| Nosy | @jcea, @scoder, @jkloth |
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 2013-09-02.00:03:41.532>
labels = ['type-feature', 'library']
title = 'Make ElementTree event handling more modular to allow custom targets for the non-blocking parser'
updated_at = <Date 2013-09-28.17:43:11.005>
user = 'https://bugs.python.org/elibendersky'
bugs.python.org fields:
activity = <Date 2013-09-28.17:43:11.005>
actor = 'scoder'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2013-09-02.00:03:41.532>
creator = 'eli.bendersky'
dependencies = []
files = []
hgrepos = []
issue_num = 18902
keywords = []
message_count = 8.0
messages = ['196758', '196830', '196832', '197552', '197590', '197606', '198526', '198537']
nosy_count = 4.0
nosy_names = ['jcea', 'scoder', 'jkloth', 'eli.bendersky']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue18902'
versions = ['Python 3.5']
Linked PRs
- gh-156888
- gh-157439
- 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
Todos los issues de python/cpython
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
-
🐛 Bug 🔔 Pending processing
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
jumpserver/jumpserver#17584 ·