argparser's subparsers.add_parser() should accept an ArgumentParser

Open
#61,406 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
cli

Research direction

Start at argparse subparsers.add_parser() and read the attached issue17204.py reproduction and patch0.diff. Determine the intended ArgumentParser input behavior from those files, then verify that the existing argparse tests cover the accepted parser form and its resulting subparser behavior.

Written by the indexing model from the issue text.

Description

pending stdlib type-feature
BPO 17204
Nosy @cjerdonek
Files
  • issue17204.py
  • patch0.diff
    		•

    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-02-14.07:01:07.036>
labels = ['type-feature', 'library']
title = "argparser's subparsers.add_parser() should accept an ArgumentParser"
updated_at = <Date 2014-10-10.04:35:04.656>
user = 'https://github.com/cjerdonek'

    bugs.python.org fields:

    activity = <Date 2014-10-10.04:35:04.656>
actor = 'paul.j3'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2013-02-14.07:01:07.036>
creator = 'chris.jerdonek'
dependencies = []
files = ['29916', '36858']
hgrepos = []
issue_num = 17204
keywords = ['patch']
message_count = 4.0
messages = ['182081', '187226', '204372', '228950']
nosy_count = 4.0
nosy_names = ['bethard', 'chris.jerdonek', 'paul.j3', 'Micka\xc3\xabl.Falck']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue17204'
versions = ['Python 3.4']

    Dominant language
    Python
    Stars
    77.2k
    Forks
    36k
    Avg merge
    1d 9h
    Merged PRs (30d)
    558

    Contributor guide

    Open the contributing guide

    First steps

    1. Read the whole issue, then the project's contributing guide.
    2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
    3. Fork the repository and make your change on a branch.
    4. Open a pull request that references the issue number.

    More from python/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.