argparse.REMAINDER fails to parse remainder correctly

Open
#58,382 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
cli

Research direction

Start with the attached reproduction files bug_argparse.py and test.py, then inspect argparse's handling of REMAINDER. Use issue14174_1.patch to understand the previously proposed direction and reproduce the reported parsing behavior. Done means the remainder is parsed as expected by the reproduction cases and the behavior is covered by a regression test.

Written by the indexing model from the issue text.

Description

stdlib type-bug
BPO 14174
Nosy @jaraco, @merwok, @cjerdonek
Files
  • bug_argparse.py: Reproduction case
  • test.py
  • issue14174_1.patch
  • 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 2012-03-02.12:08:09.567>
    labels = ['type-bug', 'library']
    title = 'argparse.REMAINDER fails to parse remainder correctly'
    updated_at = <Date 2014-07-02.06:40:46.284>
    user = 'https://bugs.python.org/rr2do2'
    

    bugs.python.org fields:

    activity = <Date 2014-07-02.06:40:46.284>
    actor = 'paul.j3'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)']
    creation = <Date 2012-03-02.12:08:09.567>
    creator = 'rr2do2'
    dependencies = []
    files = ['24705', '28165', '35824']
    hgrepos = []
    issue_num = 14174
    keywords = ['patch']
    message_count = 10.0
    messages = ['154761', '154929', '170921', '172232', '172235', '176691', '180753', '187204', '187206', '222074']
    nosy_count = 7.0
    nosy_names = ['jaraco', 'eric.araujo', 'chris.jerdonek', 'idank', 'paul.j3', 'rr2do2', 'Michael.Edwards']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = 'needs patch'
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue14174'
    versions = ['Python 2.7', 'Python 3.2', 'Python 3.3']
    

    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.