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 gvanrossum, python-dev, vstinner
Date 2014-01-31.08:49:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
_run_once() can be called more than expected if was interrupted by a signal or because the granularity is wrong. If we want to avoid that, a simple fix is just to loop again in this case. Attached patch implements that (I wrote it for Tulip, it cannot applied cleanly on Python because I added debug code to investigate this issue).

The patch should also fix the sporadic issue of signal interrupting _run_once(). The unit test should not be interrupted by a signal, but it can occur on a real application. For example when your resize a terminal.
Date User Action Args
2014-01-31 08:49:34vstinnersetrecipients: + vstinner, gvanrossum, python-dev
2014-01-31 08:49:34vstinnersetmessageid: <>
2014-01-31 08:49:34vstinnerlinkissue20452 messages
2014-01-31 08:49:33vstinnercreate