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 r.david.murray
Recipients Sworddragon, ezio.melotti, r.david.murray
Date 2013-08-26.16:48:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1377535727.18.0.731795562244.issue18836@psf.upfronthosting.co.za>
In-reply-to
Content
I wonder if you could achieve what you want (which I always hope programs I use never do[*]) by writing your own signal handler.

In any case, I don't believe there is a bug here.  This is working as designed.

[*] There are many times I have found myself leaning on ctl-C on autorepeat hoping that the ctl-c will happen at a point where the application isn't catching it, so that I can get the darn thing to abort.  I realize you are proposing to do this only to then do the abort...but what if there is a bug in your code?  I'd *much* rather see a traceback than have to fall back to 'kill'.  At least with the traceback I know the interpreter has had a chance to clean up.
History
Date User Action Args
2013-08-26 16:48:47r.david.murraysetrecipients: + r.david.murray, ezio.melotti, Sworddragon
2013-08-26 16:48:47r.david.murraysetmessageid: <1377535727.18.0.731795562244.issue18836@psf.upfronthosting.co.za>
2013-08-26 16:48:47r.david.murraylinkissue18836 messages
2013-08-26 16:48:47r.david.murraycreate