Don't close asyncio subprocess stream if it's stdin is closed
Open
Nobody has claimed this yet.
topic-asyncio
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 36805 |
|---|---|
| Nosy | @asvetlov, @1st1 |
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-05-05.18:30:29.393>
labels = ['type-bug', '3.8', 'expert-asyncio']
title = "Don't close subprocess stream if it's stdin is closed"
updated_at = <Date 2019-05-05.18:30:29.393>
user = 'https://github.com/asvetlov'
bugs.python.org fields:
activity = <Date 2019-05-05.18:30:29.393>
actor = 'asvetlov'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['asyncio']
creation = <Date 2019-05-05.18:30:29.393>
creator = 'asvetlov'
dependencies = []
files = []
hgrepos = []
issue_num = 36805
keywords = []
message_count = 1.0
messages = ['341467']
nosy_count = 2.0
nosy_names = ['asvetlov', 'yselivanov']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue36805'
versions = ['Python 3.8']
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 with the asyncio subprocess component and reproduce the behavior described in issue 36805, where closing stdin also closes a subprocess stream. Trace the relevant stream lifecycle and add or locate coverage for the case; done means the stream is not closed as a side effect of closing stdin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100