Cannot capture sys.stderr output from an uncaught exception in a multiprocessing Process using a multiprocessing Queue
Open
Nobody has claimed this yet.
stdlib
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 27081 |
|---|---|
| Nosy | @pppery, @applio, @Vgr255 |
| 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 2016-05-21.21:04:33.243>
labels = ['type-bug', 'library']
title = 'Cannot capture sys.stderr output from an uncaught exception in a multiprocessing Process using a multiprocessing Queue'
updated_at = <Date 2016-07-03.04:25:20.887>
user = 'https://github.com/pppery'
bugs.python.org fields:
activity = <Date 2016-07-03.04:25:20.887>
actor = 'davin'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2016-05-21.21:04:33.243>
creator = 'ppperry'
dependencies = []
files = ['43613']
hgrepos = []
issue_num = 27081
keywords = []
message_count = 7.0
messages = ['266026', '266028', '269733', '269736', '269737', '269738', '269750']
nosy_count = 5.0
nosy_names = ['jnoller', 'sbt', 'ppperry', 'davin', 'abarry']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue27081'
versions = ['Python 3.4']
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 attached issue27081.py example and reproduce the failure involving sys.stderr, an uncaught exception, multiprocessing.Process, and a multiprocessing.Queue. Trace the relevant multiprocessing behavior and determine how it should be tested; the issue is complete when stderr from the child process can be captured as intended without regressing existing behavior.
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
- 35/100