Let ElementTree prolog include comments and processing instructions
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 25/100
Línea de trabajo
Start with the ElementTree XML component and review the mentioned xml_prolog.diff rough draft patch. Check the linked PRs before beginning, then determine how the prolog should include comments and processing instructions; the work is done when that behavior is implemented and verified by the relevant XML tests.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
| BPO | 24287 |
|---|---|
| Nosy | @rhettinger, @scoder, @vadmium |
| Superseder | |
| Files |
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-05-26.00:54:09.997>
labels = ['expert-XML', 'type-feature']
title = 'Let ElementTree prolog include comments and processing instructions'
updated_at = <Date 2019-04-27.15:55:22.956>
user = 'https://github.com/rhettinger'
bugs.python.org fields:
activity = <Date 2019-04-27.15:55:22.956>
actor = 'scoder'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['XML']
creation = <Date 2015-05-26.00:54:09.997>
creator = 'rhettinger'
dependencies = []
files = ['39498']
hgrepos = []
issue_num = 24287
keywords = ['patch']
message_count = 4.0
messages = ['244069', '244072', '244085', '340993']
nosy_count = 4.0
nosy_names = ['rhettinger', 'scoder', 'eli.bendersky', 'martin.panter']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = '9521'
type = 'enhancement'
url = 'https://bugs.python.org/issue24287'
versions = ['Python 3.6']
Linked PRs
- gh-156719
- gh-157434
- 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
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
zostera/django-bootstrap4#894 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
use-agent-os/agent-os#3276 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
zephyrproject-rtos/zephyr#119726 ·
-
area/auth bug comp/agent P3 platform/discord type/security
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
NousResearch/hermes-agent#117848 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
zilliztech/memsearch#759 ·