Message 224249 - 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	vstinner
Recipients	BreamoreBoy, jimjjewett, jtate, pitrou, qopit, vstinner, xiaowen
Date	2014-07-29.20:58:03
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1406667483.53.0.799007236981.issue1508864@psf.upfronthosting.co.za>
In-reply-to

Content
As Antoine wrote, Condition.wait() was rewritten in Python 3.2 to implement timeout using the native OS "acquire a lock with a timeout" function. So the initial concern is already fixed. This change is huge, we are not going to backport new lock timeouts in Python 2.7, it's too risky. It's time to upgrade to Python 3! There is still a corner case when the function is interrupted by a signal, we use the system clock to recompute the new timeout. This corner case is addresses by the issue #22043.

As Antoine wrote, Condition.wait() was rewritten in Python 3.2 to implement timeout using the native OS "acquire a lock with a timeout" function. So the initial concern is already fixed. This change is huge, we are not going to backport new lock timeouts in Python 2.7, it's too risky. It's time to upgrade to Python 3!

There is still a *corner case* when the function is interrupted by a signal, we use the system clock to recompute the new timeout. This corner case is addresses by the issue #22043.

History
Date	User	Action	Args
2014-07-29 20:58:03	vstinner	set	recipients: + vstinner, jimjjewett, pitrou, qopit, jtate, xiaowen, BreamoreBoy
2014-07-29 20:58:03	vstinner	set	messageid: <1406667483.53.0.799007236981.issue1508864@psf.upfronthosting.co.za>
2014-07-29 20:58:03	vstinner	link	issue1508864 messages
2014-07-29 20:58:03	vstinner	create