argparse: suggestion for formatting optional positional args

Open
#55,917 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
cli

Research direction

Start by reviewing the argparse implementation and the referenced regroup.patch and test_regroup.py files. Determine the intended formatting for optional positional arguments from those artifacts, then use the test file to define the expected behavior and verify that the argparse tests pass.

Written by the indexing model from the issue text.

Description

3.11 stdlib type-feature
BPO 11708
Nosy @pwil3058, @akheron
Files
  • regroup.patch
  • test_regroup.py
    		•

    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 2011-03-29.04:21:10.095>
labels = ['type-feature', 'library', '3.11']
title = 'argparse: suggestion for formatting optional positional args'
updated_at = <Date 2021-12-10.15:50:50.347>
user = 'https://github.com/pwil3058'

    bugs.python.org fields:

    activity = <Date 2021-12-10.15:50:50.347>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2011-03-29.04:21:10.095>
creator = 'pwil3058'
dependencies = []
files = ['35034', '35035']
hgrepos = []
issue_num = 11708
keywords = ['patch']
message_count = 6.0
messages = ['132462', '141050', '149543', '198038', '217153', '217154']
nosy_count = 4.0
nosy_names = ['bethard', 'pwil3058', 'petri.lehtinen', 'paul.j3']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue11708'
versions = ['Python 3.11']

    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.