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 poq
Recipients eric.araujo, neologix, pitrou, poq, r.david.murray, telmich
Date 2012-03-23.14:42:17
SpamBayes Score 1.93186e-09
Marked as misclassified No
Message-id <1332513738.43.0.395081755722.issue14228@psf.upfronthosting.co.za>
In-reply-to
Content
> No, the point is that the exception may be caused by a real bug and having the traceback is tremendously useful to debug such situations. [...] KeyboardInterrupt is not different in this regard from, say, ZeroDivisionError.

KeyboardInterrupt *is* different though. It is caused by the user instead of by any bug.

Of course, it can still be useful to know where the program was interrupted, so showing a traceback for KeyboardInterrupt by default makes sense IMO.

> As I said, a possible solution is to allow users to alter the default signal handling (using an env var).

Why an environment variable instead of a command line switch (as suggested by Ian Jackson)? Shouldn't a script be able to decide for itself how it handles signals?
History
Date User Action Args
2012-03-23 14:42:18poqsetrecipients: + poq, pitrou, eric.araujo, r.david.murray, neologix, telmich
2012-03-23 14:42:18poqsetmessageid: <1332513738.43.0.395081755722.issue14228@psf.upfronthosting.co.za>
2012-03-23 14:42:17poqlinkissue14228 messages
2012-03-23 14:42:17poqcreate