Message 147319 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	stacktic
Recipients	stacktic
Date	2011-11-08.22:11:27
SpamBayes Score	2.0901037e-07
Marked as misclassified	No
Message-id	<1320790288.25.0.363329173413.issue13373@psf.upfronthosting.co.za>
In-reply-to

Content
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)

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)

History
Date	User	Action	Args
2011-11-08 22:11:28	stacktic	set	recipients: + stacktic
2011-11-08 22:11:28	stacktic	set	messageid: <1320790288.25.0.363329173413.issue13373@psf.upfronthosting.co.za>
2011-11-08 22:11:27	stacktic	link	issue13373 messages
2011-11-08 22:11:27	stacktic	create