ArgumentParser nested subparsers resolve paths in improper order

Open
#86,623 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start at the ArgumentParser nested-subparser handling and reproduce the path-resolution order described by the issue. Trace how nested subcommands are resolved, then add a regression test demonstrating the improper order; done means nested subparsers resolve their paths correctly without breaking existing argparse behavior.

Written by the indexing model from the issue text.

Description

3.10 3.8 (EOL) 3.9 (EOL) stdlib type-bug
BPO 42457
Nosy @rhettinger, @carsonwilber

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 2020-11-25.04:36:54.586>
labels = ['type-bug', '3.8', '3.9', '3.10']
title = 'ArgumentParser nested subparsers resolve paths in improper order'
updated_at = <Date 2020-11-25.06:13:00.376>
user = 'https://github.com/carsonwilber'

bugs.python.org fields:

activity = <Date 2020-11-25.06:13:00.376>
actor = 'izbyshev'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2020-11-25.04:36:54.586>
creator = 'carsonwilber'
dependencies = []
files = []
hgrepos = []
issue_num = 42457
keywords = []
message_count = 1.0
messages = ['381789']
nosy_count = 2.0
nosy_names = ['rhettinger', 'carsonwilber']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue42457'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']

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.