Message 187063 - 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	pitrou
Recipients	bkabrda, pitrou, yarda
Date	2013-04-16.09:45:02
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1366105502.86.0.474438751367.issue17748@psf.upfronthosting.co.za>
In-reply-to

Content
Locks in 2.7 don't support a timeout, which is why Condition.wait has a polling loop. The comment explains it all: # Balancing act: We can't afford a pure busy loop, so we # have to sleep; but if we sleep the whole timeout time, # we'll be unresponsive. Lock timeouts are a new feature in 3.2 and therefore won't be backported in 2.7, which is in bugfix mode. Consider it a good reason to switch to 3.x :-) (yes, we are aware about the power consumption issue)

Locks in 2.7 don't support a timeout, which is why Condition.wait has a polling loop. The comment explains it all:

 # Balancing act:  We can't afford a pure busy loop, so we
 # have to sleep; but if we sleep the whole timeout time,
 # we'll be unresponsive. 

Lock timeouts are a new feature in 3.2 and therefore won't be backported in 2.7, which is in bugfix mode. Consider it a good reason to switch to 3.x :-)

(yes, we are aware about the power consumption issue)

History
Date	User	Action	Args
2013-04-16 09:45:02	pitrou	set	recipients: + pitrou, bkabrda, yarda
2013-04-16 09:45:02	pitrou	set	messageid: <1366105502.86.0.474438751367.issue17748@psf.upfronthosting.co.za>
2013-04-16 09:45:02	pitrou	link	issue17748 messages
2013-04-16 09:45:02	pitrou	create