Steffen Daode Nurpmeso <sdao...@googlemail.com> added the comment:
By the way, in another thread i've seen a link to issue960406,
where Guido van Rossum states (in msg46074):
Ideally, ^C should always cause the signal handler for
SIGINT to be called, and the KeyboardInterrupt should be
generated by the default SIGINT handler
Thus removing ISIG contradicts approaches Python has chosen to
use a long time ago (tracks get lost, as always).
Just in case anybody is not convinced yet that ISIG has to go.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue11236>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
