Ralf Schmitt added the comment: Those who want to legitimately catch SIGSEGV will end up with an uninterruptible python process using 100 % CPU on a real segmentation fault. But, then I can live with the current behaviour.
__________________________________ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1215> __________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
