suggesting option to raise exception if process exits nonzero in `with subprocess.Popen(...):`
Open
Nobody has claimed this yet.
3.9 (EOL)
stdlib
topic-subprocess
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 37184 |
|---|---|
| Nosy | @gpshead, @ericvsmith |
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-06-06.22:16:29.584>
labels = ['type-bug', 'library', '3.9']
title = 'suggesting option to raise exception if process exits nonzero in `with subprocess.Popen(...):`'
updated_at = <Date 2019-06-11.18:03:12.964>
user = 'https://bugs.python.org/nlevitt'
bugs.python.org fields:
activity = <Date 2019-06-11.18:03:12.964>
actor = 'nlevitt'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-06-06.22:16:29.584>
creator = 'nlevitt'
dependencies = []
files = []
hgrepos = []
issue_num = 37184
keywords = []
message_count = 5.0
messages = ['344880', '344882', '344883', '344886', '345257']
nosy_count = 3.0
nosy_names = ['gregory.p.smith', 'eric.smith', 'nlevitt']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue37184'
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
The issue concerns the subprocess.Popen context manager, but it names no source files or tests and does not define the proposed option's behavior. Start by locating the subprocess library implementation and its existing tests, then clarify the API and nonzero-exit semantics with maintainers; done means an agreed behavior covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100