subprocess on windows leaks stdout/stderr handle to child process when stdout/stderr overridden

Open
#70,918 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python

Research direction

The issue concerns Python's Windows subprocess handling when stdout or stderr is overridden, but it names no files, tests, or entry points. Begin by locating the Windows subprocess handle-inheritance implementation and establish a reproduction; done means the child process no longer receives the unintended stdout/stderr handles.

Written by the indexing model from the issue text.

Description

OS-windows topic-subprocess type-bug
BPO 26731
Nosy @pfmoore, @vstinner, @tjguk, @zware, @zooba

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 2016-04-10.20:21:52.982>
labels = ['OS-windows', 'performance']
title = 'subprocess on windows leaks stdout/stderr handle to child process when stdout/stderr overridden'
updated_at = <Date 2016-04-12.23:02:50.003>
user = 'https://bugs.python.org/saifujinaro'

bugs.python.org fields:

activity = <Date 2016-04-12.23:02:50.003>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Windows']
creation = <Date 2016-04-10.20:21:52.982>
creator = 'saifujinaro'
dependencies = []
files = []
hgrepos = []
issue_num = 26731
keywords = []
message_count = 3.0
messages = ['263149', '263156', '263283']
nosy_count = 6.0
nosy_names = ['paul.moore', 'vstinner', 'tim.golden', 'zach.ware', 'steve.dower', 'saifujinaro']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'resource usage'
url = 'https://bugs.python.org/issue26731'
versions = ['Python 2.7']

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.