➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author sdaoden
Recipients asvetlov, belopolsky, benjamin.peterson, eric.araujo, gregory.p.smith, orsenthil, pajs@fodder.org.uk, pitrou, sdaoden, valhallasw
Date 2011-03-24.10:30:16
SpamBayes Score 0.00011789941
Marked as misclassified No
Message-id <20110324103010.GK33873@sherwood.local>
In-reply-to <1300941126.17.0.805942520947.issue11236@psf.upfronthosting.co.za>
Content 
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.
History
Date User Action Args
2011-03-24 10:30:17sdaodensetrecipients: + sdaoden, gregory.p.smith, belopolsky, orsenthil, pitrou, benjamin.peterson, pajs@fodder.org.uk, eric.araujo, asvetlov, valhallasw
2011-03-24 10:30:17sdaodenlinkissue11236 messages
2011-03-24 10:30:16sdaodencreate