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 Bill.Sobel
Recipients Bill.Sobel, bkabrda, pitrou, yarda
Date 2013-10-09.21:58:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1381355928.72.0.499734727495.issue17748@psf.upfronthosting.co.za>
In-reply-to
Content
I'd like to suggest a easy fix here (I saw this was closed, but the posters were asking for a behavior change).  With this fix there is no behavior change to callers or new parameters to the API.


if remaining >= 4.0:
    maxDelay = 1
else:
    maxDelay = .05
delay = min(delay * 2, remaining, maxDelay)

With this fix the loop waits 1 second until it is 'close' to the expiration time then goes into its normal 20 times per-second check.  For long waits this is what is causing the power issue and is alleviated by throttling back on the check when not close to expiration.
History
Date User Action Args
2013-10-09 21:58:48Bill.Sobelsetrecipients: + Bill.Sobel, pitrou, bkabrda, yarda
2013-10-09 21:58:48Bill.Sobelsetmessageid: <1381355928.72.0.499734727495.issue17748@psf.upfronthosting.co.za>
2013-10-09 21:58:48Bill.Sobellinkissue17748 messages
2013-10-09 21:58:48Bill.Sobelcreate