➜

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 neologix
Recipients felipecruz, neologix, pitrou, vstinner
Date 2012-10-03.08:40:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM28_E4WkeDUX=mhwQ4hyKg_kyxAY6kQJZqfFAJ__D4DfQ@mail.gmail.com>
In-reply-to <CAMpsgwaYXbpd+kgdXwry518m0zEmjvL8+wnmLEqzpaocVptZEA@mail.gmail.com>
Content 
> A signal handler can be called anymore, anywhere. How do you handle such
> exception in an application? "handle": do something better than exit the
> apllication.

Well, chances are you won't, but failing with an explicit error
message is better than silently failing to deliver signals (which may
result in a deadlock, for example).
History
Date User Action Args
2012-10-03 08:40:39neologixsetrecipients: + neologix, pitrou, vstinner, felipecruz
2012-10-03 08:40:39neologixlinkissue16105 messages
2012-10-03 08:40:39neologixcreate