Command line option with &/or without a space results in the same outcome
Open
Nobody has claimed this yet.
3.9 (EOL)
docs
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 38690 |
|---|---|
| Nosy | @ned-deily, @jgors |
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 2019-11-05.00:04:15.972>
labels = ['type-bug', '3.9', 'docs']
title = 'Command line option with &/or without a space results in the same outcome'
updated_at = <Date 2019-11-05.10:49:07.760>
user = 'https://github.com/jgors'
bugs.python.org fields:
activity = <Date 2019-11-05.10:49:07.760>
actor = 'ned.deily'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2019-11-05.00:04:15.972>
creator = 'jgors'
dependencies = []
files = []
hgrepos = []
issue_num = 38690
keywords = []
message_count = 2.0
messages = ['355985', '356019']
nosy_count = 3.0
nosy_names = ['ned.deily', 'docs@python', 'jgors']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue38690'
versions = ['Python 3.9']
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 reading the migrated BPO issue 38690 and the issue's command-line documentation context; no file or test is named here. Identify the relevant documentation entry and verify the expected distinction between options with and without spaces; done means the documented behavior is accurate and unambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100