Subprocess timeout causes output to be returned as bytes in text mode
Open
Nobody has claimed this yet.
stdlib
topic-subprocess
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 43431 |
|---|---|
| Nosy | @giampaolo, @eryksun |
| 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 2021-03-08.05:41:46.323>
labels = ['3.8', 'type-bug', 'library', '3.9', '3.10']
title = 'Subprocess timeout causes output to be returned as bytes in text mode'
updated_at = <Date 2021-03-30.18:57:45.244>
user = 'https://bugs.python.org/macdjord'
bugs.python.org fields:
activity = <Date 2021-03-30.18:57:45.244>
actor = 'eryksun'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-03-08.05:41:46.323>
creator = 'macdjord'
dependencies = []
files = ['49856']
hgrepos = []
issue_num = 43431
keywords = []
message_count = 3.0
messages = ['388257', '388265', '388272']
nosy_count = 3.0
nosy_names = ['giampaolo.rodola', 'eryksun', 'macdjord']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue43431'
versions = ['Python 3.8', 'Python 3.9', '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
Start by running the attached test_subprocess.py to reproduce the timeout case in text mode. Then inspect the subprocess library implementation and existing subprocess tests; done means timed-out output remains text rather than bytes and the regression is covered by a test.
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
- Mostly clear
- Newbie friendliness
- 42/100