[New-bugs-announce] [issue13373] Unexpected blocking call to multiprocessing.Queue.get with a timeout
Arnaud Ysmal
report at bugs.python.org
Tue Nov 8 23:11:28 CET 2011
New submission from Arnaud Ysmal <stacktic at netbsd.org>:
Using get(timeout=1) on a multiprocessing.Queue sometimes leads to a blocking get.
It seems that there is no check whether the timeout has expired after acquiring the lock but before the time.time(), which can cause a call to poll() with a negative timeout.
(patch attached)
----------
components: Library (Lib)
files: multiprocessing_queues.patch
keywords: patch
messages: 147319
nosy: stacktic
priority: normal
severity: normal
status: open
title: Unexpected blocking call to multiprocessing.Queue.get with a timeout
type: behavior
Added file: http://bugs.python.org/file23638/multiprocessing_queues.patch
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue13373>
_______________________________________
More information about the New-bugs-announce
mailing list