New submission from Arnaud Ysmal <stack...@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 <rep...@bugs.python.org> <http://bugs.python.org/issue13373> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
