argparse: parser aliases in subparsers stores alias in dest variable
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 36664 |
|---|---|
| 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 2019-04-18.23:30:32.042>
labels = ['3.7', 'type-feature', 'library']
title = 'argparse: parser aliases in subparsers stores alias in dest variable'
updated_at = <Date 2019-11-01.01:51:18.147>
user = 'https://bugs.python.org/PeterMcEldowney'
bugs.python.org fields:
activity = <Date 2019-11-01.01:51:18.147>
actor = 'paul.j3'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-04-18.23:30:32.042>
creator = 'Peter McEldowney'
dependencies = []
files = ['48275']
hgrepos = []
issue_num = 36664
keywords = []
message_count = 5.0
messages = ['340515', '340525', '340595', '355759', '355779']
nosy_count = 3.0
nosy_names = ['paul.j3', 'nemeskeyd', 'Peter McEldowney']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue36664'
versions = ['Python 3.7']
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.
Research direction
Start with the linked sample.py to reproduce how an argparse subparser alias is written to the dest variable. Trace that behavior into CPython's argparse implementation and identify the existing command-line parsing tests to extend; done means the alias behavior matches the intended dest value without regressing subparser parsing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100