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 pitrou, telmich
Date 2012-03-08.19:06:15
SpamBayes Score 6.80664e-07
Marked as misclassified No
Message-id <1331233326.3386.1.camel@localhost.localdomain>
In-reply-to <>
> Regarding "feature request": I think this is a *bug*, not a feature
> request: For me, it is impossible to handle SIGINT correctly with my
> code, because it is half-handled (exception raised, but impossible to
> catch) by python itself.

In the trace you just posted, I see "caught signint in parent" (at the
beginning), so the exception was indeed caught.

> When starting to read "python shipped code" (i.e. stuff that comes
> with python and is always loaded), it should either implement a
> handler for sigint OR have sigint signal handler set to ignore.

Well, it does implement a SIGINT handler, and that handler raises
KeyboardInterrupt. QED. You can override that behaviour and register
your own handler using the standard "signal" module.
Date User Action Args
2012-03-08 19:06:16pitrousetrecipients: + pitrou, telmich
2012-03-08 19:06:15pitroulinkissue14228 messages
2012-03-08 19:06:15pitroucreate