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-14.19:32:44
SpamBayes Score 0.256987
Marked as misclassified No
Message-id <1200339166.41.0.384410481712.issue1215@psf.upfronthosting.co.za>
In-reply-to
Content
In essence, it's a weakness of the POSIX API that it doesn't distinguish
synchronous from asynchronous signals.

The consequences of either approach seem minor though.  I cannot imagine
a sane use case for catching SIGSEGV, but documentation changes should
be sufficient anyway.

Suggested wording, if you take the documentation-only approach:
"Because of the precarious nature of how synchronously-generated signals
must be handled, it is impossible to handle them correctly from python.
 You should never install handlers for synchronously-generated signals,
such as SIGSEGV and SIGFPE."
History
Date User Action Args
2008-01-14 19:32:46Rhamphoryncussetspambayes_score: 0.256987 -> 0.256987
recipients: + Rhamphoryncus, gvanrossum, tebeka, schmir
2008-01-14 19:32:46Rhamphoryncussetspambayes_score: 0.256987 -> 0.256987
messageid: <1200339166.41.0.384410481712.issue1215@psf.upfronthosting.co.za>
2008-01-14 19:32:45Rhamphoryncuslinkissue1215 messages
2008-01-14 19:32:44Rhamphoryncuscreate