subprocess.communicate with timeout 0 and already terminated process generates TimeoutExpired on Linux
Open
Nobody has claimed this yet.
stdlib
topic-subprocess
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 29472 |
|---|---|
| Nosy | @Griffon26, @spoorcc |
| 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-02-07.11:57:14.624>
labels = ['type-bug', 'library']
title = 'subprocess.communicate with timeout 0 and already terminated process generates TimeoutExpired on Linux'
updated_at = <Date 2017-02-07.12:36:53.465>
user = 'https://github.com/Griffon26'
bugs.python.org fields:
activity = <Date 2017-02-07.12:36:53.465>
actor = 'spoorcc'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-02-07.11:57:14.624>
creator = 'Griffon26'
dependencies = []
files = ['46557']
hgrepos = []
issue_num = 29472
keywords = []
message_count = 1.0
messages = ['287230']
nosy_count = 2.0
nosy_names = ['Griffon26', 'spoorcc']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue29472'
versions = ['Python 3.6']
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 running the minimal reproduction in test.py on Linux and inspect how subprocess.communicate handles timeout=0 for an already terminated process. Done means that this case no longer raises TimeoutExpired while preserving the expected timeout behavior for processes that have not terminated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100