subprocess: Calling Popen.communicate() after Popen.stdout.read() returns an empty string
Open
Nobody has claimed this yet.
3.10
stdlib
topic-subprocess
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 41406 |
|---|---|
| Nosy | @gpshead, @vstinner, @gst, @FrostMing |
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 2020-07-27.08:26:24.981>
labels = ['type-bug', 'library', '3.10']
title = 'subprocess: Calling Popen.communicate() after Popen.stdout.read() returns an empty string'
updated_at = <Date 2020-08-04.01:55:39.697>
user = 'https://github.com/frostming'
bugs.python.org fields:
activity = <Date 2020-08-04.01:55:39.697>
actor = 'gregory.p.smith'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-07-27.08:26:24.981>
creator = 'Frost Ming'
dependencies = []
files = []
hgrepos = []
issue_num = 41406
keywords = []
message_count = 4.0
messages = ['374366', '374436', '374769', '374783']
nosy_count = 4.0
nosy_names = ['gregory.p.smith', 'vstinner', 'gstarck', 'Frost Ming']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue41406'
versions = ['Python 3.10']
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 source file or test is named. Start by reproducing the interaction between Popen.stdout.read() and Popen.communicate(), then inspect the subprocess implementation and existing tests; done requires a confirmed expected behavior and regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100