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 pitrou
Recipients eric.araujo, neologix, pitrou, poq, r.david.murray, telmich
Date 2012-03-23.13:32:29
SpamBayes Score 6.99334e-11
Marked as misclassified No
Message-id <1332509264.3416.5.camel@localhost.localdomain>
In-reply-to <1332508563.54.0.0213162984985.issue14228@psf.upfronthosting.co.za>
Content
> Don't be offended, but this looks like a software coded by a 12 years
> old, who is proud about it and does not accept an error being an error
> and insists on doing it right, although it's a common understanding
> that throwing errors in non error situations.

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.
So the Python runtime by default prints out the whole traceback when an
uncaught exception occurs. KeyboardInterrupt is not different in this
regard from, say, ZeroDivisionError.

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

(note that, AFAICT, you're the first to report a problem here, although
this behaviour has existed for ages)
History
Date User Action Args
2012-03-23 13:32:30pitrousetrecipients: + pitrou, eric.araujo, r.david.murray, neologix, poq, telmich
2012-03-23 13:32:29pitroulinkissue14228 messages
2012-03-23 13:32:29pitroucreate