[issue6901] Runaway programs often become unresponsive to CTRL-C

Bernie H. Innocenti added the comment: Ok -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue6901] Runaway programs often become unresponsive to CTRL-C

Benjamin Peterson added the comment: Regardless of whether this is a good idea or not, it's too broad a change for the bug tracker. Please bring it up on python-ideas if you wish to pursue the topic. -- ___ Python tracker

[issue6901] Runaway programs often become unresponsive to CTRL-C

Bernie H. Innocenti added the comment: > This is a fundemental behavior that will never change. If you > dislike it, you can remove the signal handler for it with the > signal module. What? We could break the syntax of "print" statements and cannot change this minor detail that afftects many 1

[issue6901] Runaway programs often become unresponsive to CTRL-C

Benjamin Peterson added the comment: This is a fundemental behavior that will never change. If you dislike it, you can remove the signal handler for it with the signal module. -- nosy: +benjamin.peterson resolution: -> works for me status: open -> closed __

[issue6901] Runaway programs often become unresponsive to CTRL-C

New submission from Bernie H. Innocenti : On startup, the Python interpreter changes the default behavior of SIGINT, which results in many Python programs to ignore the keyboard interrupt exactly in the situations when users are most likely to use it (i.e.: when the program becomes unresponsive)