Add "necessarily inclusive" groups to argparse

Open
#55,797 46 comments 60 reactions 1 assignee View on GitHub

@savannahostrowski is already working on this.

Since Nov 21, 2024.

  • #150981 by @savannahostrowski — open

Assessment

This issue has not been assessed yet.

Description

stdlib type-feature
BPO 11588
Nosy @cjmayo, @ikelos, @IIIIllllIIIIllllIIIIllllIIIIllllIIIIll, @iforapsy
Files
  • patch_w_mxg2.diff
  • example1.py
  • issue11588_4.py
  • usagegroup.py
  • usage_2.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 2011-03-17.15:51:29.761>
labels = ['type-feature']
title = 'Add "necessarily inclusive" groups to argparse'
updated_at = <Date 2019-11-07.02:24:58.703>
user = 'https://bugs.python.org/JohnDidion'

    bugs.python.org fields:

    activity = <Date 2019-11-07.02:24:58.703>
actor = 'iforapsy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2011-03-17.15:51:29.761>
creator = 'John.Didion'
dependencies = []
files = ['34176', '34193', '34285', '35608', '36553']
hgrepos = []
issue_num = 11588
keywords = ['patch']
message_count = 17.0
messages = ['131262', '132241', '134560', '211240', '211261', '211878', '211947', '212228', '212243', '212733', '215777', '220419', '226324', '226469', '265734', '286582', '294569']
nosy_count = 9.0
nosy_names = ['bethard', 'cjmayo', 'ikelos', 'xuanji', 'John.Didion', 'manveru', 'paul.j3', 'pgacv2', 'iforapsy']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue11588'
versions = ['Python 3.3']

    Linked PRs
    • gh-150981
    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.