[issue13373] Unexpected blocking call to multiprocessing.Queue.get with a timeout

New submission from Arnaud Ysmal : 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.

[issue13373] Unexpected blocking call to multiprocessing.Queue.get with a timeout

Changes by Antoine Pitrou : -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue13373] Unexpected blocking call to multiprocessing.Queue.get with a timeout

Changes by Antoine Pitrou : -- nosy: +neologix stage: -> patch review versions: +Python 2.7, Python 3.2, Python 3.3 ___ Python tracker ___ __

[issue13373] Unexpected blocking call to multiprocessing.Queue.get with a timeout

Roundup Robot added the comment: New changeset e7b6dca28a2f by Antoine Pitrou in branch '2.7': Issue #13373: multiprocessing.Queue.get() could sometimes block indefinitely http://hg.python.org/cpython/rev/e7b6dca28a2f New changeset 9328080a19c0 by Antoine Pitrou in branch '3.2': Issue #13373: m

[issue13373] Unexpected blocking call to multiprocessing.Queue.get with a timeout

Antoine Pitrou added the comment: Patch committed, thank you for contributing! -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker _