Explain why it is recommended to pass args as a string rather than as a sequence If shell is True
Open
Nobody has claimed this yet.
docs
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 30079 |
|---|---|
| Nosy | @bitdancer, @eryksun |
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-04-16.03:10:04.802>
labels = ['type-feature', 'docs']
title = 'Explain why it is recommended to pass args as a string rather than as a sequence If shell is True'
updated_at = <Date 2017-04-16.16:51:02.875>
user = 'https://bugs.python.org/iMath'
bugs.python.org fields:
activity = <Date 2017-04-16.16:51:02.875>
actor = 'r.david.murray'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2017-04-16.03:10:04.802>
creator = 'iMath'
dependencies = []
files = []
hgrepos = []
issue_num = 30079
keywords = []
message_count = 5.0
messages = ['291733', '291734', '291735', '291755', '291756']
nosy_count = 4.0
nosy_names = ['r.david.murray', 'docs@python', 'eryksun', 'iMath']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue30079'
versions = []
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
No documentation file or test is named. Start by locating the Python documentation for subprocess arguments and shell=True, then identify the passage describing string versus sequence arguments; done means the recommendation's rationale is clearly explained in the relevant documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100