argparse: relative include of config files
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 30421 |
|---|---|
| Nosy | @mlouielu, @efficiosoft |
| PRs | |
| Files |
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 2017-05-21.08:15:42.296>
labels = ['3.7', 'type-bug', 'library']
title = 'argparse: relative include of config files'
updated_at = <Date 2017-09-02.16:37:28.005>
user = 'https://github.com/efficiosoft'
bugs.python.org fields:
activity = <Date 2017-09-02.16:37:28.005>
actor = 'paul.j3'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-05-21.08:15:42.296>
creator = 'roschi'
dependencies = []
files = ['46881', '46882']
hgrepos = []
issue_num = 30421
keywords = ['patch']
message_count = 3.0
messages = ['294086', '294096', '294098']
nosy_count = 4.0
nosy_names = ['bethard', 'paul.j3', 'louielu', 'roschi']
pr_nums = ['1698']
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue30421'
versions = ['Python 3.6', 'Python 3.7']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked PR #1698 and the two attached files, argparse_relative_includes.patch and argparse_relative_includes2.patch. Compare their proposed behavior with argparse's current config-file include handling; the work is done when the intended relative-include behavior is implemented and the existing patch concerns are resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100