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 martin.panter
Recipients martin.panter, ryan.petrello
Date 2016-10-18.03:16:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1476760603.81.0.902934975894.issue28466@psf.upfronthosting.co.za>
In-reply-to
Content
This is by design; see PEP 475, and the documentation <https://docs.python.org/3.5/library/time.html#time.sleep>.

If you make your signal handler raise an exception, it will interrupt the sleep() call most of the time. But if the signal happens to be received just before the sleep() call is about to be entered, the handler will only be run when the underlying OS sleep() call returns 10 s later.
History
Date User Action Args
2016-10-18 03:16:43martin.pantersetrecipients: + martin.panter, ryan.petrello
2016-10-18 03:16:43martin.pantersetmessageid: <1476760603.81.0.902934975894.issue28466@psf.upfronthosting.co.za>
2016-10-18 03:16:43martin.panterlinkissue28466 messages
2016-10-18 03:16:43martin.pantercreate