[Python-Dev] Default SIGINT handling dangerous?

R. David Murray rdmurray at bitdance.com
Sat Dec 14 17:14:34 CET 2013

On Sat, 14 Dec 2013 15:14:10 +0100, "Jurko Gospodneti" <jurko.gospodnetic at pke.hr> wrote:
>    My scripts replace the default SIGINT/SIGBREAK signal handlers as 
> soon as possible, and everything works great after that, but things get 
> ugly if Ctrl-C is pressed before the script gets a chance to do this. I 
> could even live with an 'exit with an ugly traceback', but having the 
> process hang or fail so that Windows reports it as non-responding or 
> reports it as 'stopped working' and offers to send failure information 
> to Microsoft? That just leaves a bad taste in my mouth. :-(

This sounds like a more troubling variation on the issue raised in
issue 14288 (http://bugs.python.org/issue14228).  The solution proposed 
there would appear to be something that would help you, so you might
want to chime in on that issue.

(I'll be curious to see the responses to the other points you raise.)


More information about the Python-Dev mailing list