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 Rhamphoryncus
Recipients Rhamphoryncus, gvanrossum, schmir, tebeka
Date 2008-01-12.23:20:22
SpamBayes Score 0.0013193
Marked as misclassified No
Message-id <1200180024.28.0.414781712609.issue1215@psf.upfronthosting.co.za>
In-reply-to
Content
The warning in the documentation should be strengthened.  Python simply
does not and cannot support synchronously-generated signals.

It is possible to send a normally synchronous signal asynchronously,
such as the os.kill() Ralf mentioned, so it's theoretically possible to
use custom handlers for them.  However, I can't think of any real use
cases, and having such a handler would be asking for trouble if a real
synchronously-generated signal was produced.  I guess that's an argument
for not allowing custom handlers. ;)

Suggested documentation:
"Because of the precarious nature of how synchronously-generated signals
must be handled, the signal module does not allow installing handlers
for them.  This includes SIGSEGV, SIGFPE, SIGBUS, SIGILL, SIGABRT..."

I haven't been able to find a canonical list if synchronously-generated
signals.  Furthermore, I've seen conflicting claims about SIGABRT.
History
Date User Action Args
2008-01-12 23:20:24Rhamphoryncussetspambayes_score: 0.0013193 -> 0.0013193
recipients: + Rhamphoryncus, gvanrossum, tebeka, schmir
2008-01-12 23:20:24Rhamphoryncussetspambayes_score: 0.0013193 -> 0.0013193
messageid: <1200180024.28.0.414781712609.issue1215@psf.upfronthosting.co.za>
2008-01-12 23:20:23Rhamphoryncuslinkissue1215 messages
2008-01-12 23:20:22Rhamphoryncuscreate