argparse: Issue 15906 patch; positional with nargs='*' and string default

Open
#61,452 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
cli

Research direction

The issue concerns argparse positional arguments using nargs='*' with a string default, but it names no files, tests, or expected replacement behavior. Start by reproducing that argument-parsing case and locating the argparse implementation and related tests; the issue needs an agreed behavior and a regression test before completion can be verified.

Written by the indexing model from the issue text.

Description

stdlib type-bug
BPO 17250
Nosy @cjerdonek, @mblahay

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-20.04:58:17.069>
labels = ['type-bug', 'library']
title = "argparse: Issue 15906 patch; positional with nargs='*' and string default"
updated_at = <Date 2019-05-27.03:20:17.096>
user = 'https://bugs.python.org/paulj3'

bugs.python.org fields:

activity = <Date 2019-05-27.03:20:17.096>
actor = 'mblahay'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2013-02-20.04:58:17.069>
creator = 'paul.j3'
dependencies = []
files = []
hgrepos = []
issue_num = 17250
keywords = []
message_count = 4.0
messages = ['182469', '223057', '223159', '343605']
nosy_count = 4.0
nosy_names = ['bethard', 'chris.jerdonek', 'paul.j3', 'mblahay']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue17250'
versions = ['Python 2.7', '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.