Message133961
| Author |
vstinner |
| Recipients |
pitrou, python-dev, vstinner |
| Date |
2011年04月18日.10:52:48 |
| SpamBayes Score |
7.335721e-06 |
| Marked as misclassified |
No |
| Message-id |
<1303123970.27664.6.camel@marge> |
| In-reply-to |
<1303123231.01.0.0893225357862.issue11768@psf.upfronthosting.co.za> |
| Content |
Le lundi 18 avril 2011 à 10:40 +0000, STINNER Victor a écrit :
> Attached patch should fix this issue:
>
> - signal_handler() and PyErr_SetInterrupt() only call Py_AddPendingCall() on the first signal (if is_tripped is zero): it should fix the deadlock and it is a micro optimization (win-win !)
Tested on OSX: yes, it does fix this issue.
Should I apply the fix on 2.7, 3.1, 3.2 and 3.3? (or only 3.3) |
|