argparse: 'resolve' conflict handler damages the actions of the parent parser
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
Research direction
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.
Written by the indexing model from the issue text.
Description
| 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']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100