Repository navigation
[doc] multiprocessing.Queue fails intermittently with "Broken pipe" #82742
Description
| BPO | 38561 |
|---|---|
| Nosy | @iritkatriel |
| 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 2019-10-23.01:40:48.912>
labels = ['type-bug', '3.9', '3.10', '3.11', 'library', 'docs']
title = '[doc] multiprocessing.Queue fails intermittently with "Broken pipe"'
updated_at = <Date 2022-01-19.10:16:13.205>
user = 'https://bugs.python.org/SamuelGrayson'bugs.python.org fields:
activity = <Date 2022-01-19.10:16:13.205>
actor = 'iritkatriel'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'Library (Lib)']
creation = <Date 2019-10-23.01:40:48.912>
creator = 'Samuel Grayson'
dependencies = []
files = ['48674']
hgrepos = []
issue_num = 38561
keywords = []
message_count = 2.0
messages = ['355204', '410932']
nosy_count = 3.0
nosy_names = ['docs@python', 'Samuel Grayson', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue38561'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
Activity
SamuelGrayson commentedon Oct 23, 2019
See this SO post for more details
iritkatriel commentedon Jan 19, 2022
I don't think you're supposed to close the queue more than once. The documentation can be improved on that. Currently the documentation of close is:
https://docs.python.org/3/library/multiprocessing.html#multiprocessing.Queue.close
That could be read to imply to each process needs to indicate when it is done.
[-]multiprocessing.Queue fails intermittently with "Broken pipe"[/-][+][doc] multiprocessing.Queue fails intermittently with "Broken pipe"[/+]slateny commentedon May 4, 2022
Related to #80025 (and possibly the referenced #91185 and #31913)
geryogam commentedon May 11, 2022
@JelleZijlstra, could you also close this issue now that it has been fixed in PR #31913?