argparse: 'resolve' conflict handler damages the actions of the parent parser
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 38/100
Línea de trabajo
Start by reviewing the historical sample3.py and patch_1.diff linked in the issue, then locate the current argparse conflict-resolution implementation and its tests. Reproduce the parent-parser behavior described in the title and verify that resolving a conflict no longer damages the parent actions, with regression coverage for the case.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
| BPO | 22401 |
|---|---|
| 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 2014-09-14.05:46:38.711>
labels = ['tests', 'type-bug', 'library', 'docs']
title = "argparse: 'resolve' conflict handler damages the actions of the parent parser"
updated_at = <Date 2021-01-27.18:49:22.288>
user = 'https://bugs.python.org/paulj3'
bugs.python.org fields:
activity = <Date 2021-01-27.18:49:22.288>
actor = 'kcwu'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'Library (Lib)', 'Tests']
creation = <Date 2014-09-14.05:46:38.711>
creator = 'paul.j3'
dependencies = []
files = ['36728', '36773']
hgrepos = []
issue_num = 22401
keywords = ['patch']
message_count = 8.0
messages = ['226862', '226982', '228137', '262314', '262318', '262365', '262366', '262373']
nosy_count = 5.0
nosy_names = ['bethard', 'kcwu', 'docs@python', 'paul.j3', 'deckar01']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue22401'
versions = ['Python 2.7', '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
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
-
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 74/100
bancolombia/sentinel#23 ·
-
test md AbiertoCI
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100