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 flavio
Recipients flavio, pitrou
Date 2015-09-13.13:40:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1442151642.39.0.456899707142.issue25084@psf.upfronthosting.co.za>
In-reply-to
Content
threading.Condition.wait(timeout=x) is implemented in python 2  as a semi-busy loop which causes cpu wakeups and unexpected cpu use.

I think this is somewhat problematic since it causes problems in all modules which use that method, such as Queue.get() when used with a timeout.

This issue has been reported and "fixed" in red hat based distributions in a way which i find problematic, as detailed here:
https://bugzilla.redhat.com/show_bug.cgi?id=1230802

The attached patch backports the following change from py3 to fix the problem:
https://hg.python.org/cpython/rev/01d1fd775d16/
History
Date User Action Args
2015-09-13 13:40:44flaviosetrecipients: + flavio, pitrou
2015-09-13 13:40:42flaviosetmessageid: <1442151642.39.0.456899707142.issue25084@psf.upfronthosting.co.za>
2015-09-13 13:40:42flaviolinkissue25084 messages
2015-09-13 13:40:42flaviocreate