Message 76995 - Python tracker

➜

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	georg.brandl
Recipients	Rhamphoryncus, georg.brandl, gvanrossum, schmir, tebeka
Date	2008-12-05.09:42:13
SpamBayes Score	1.0513423e-05
Marked as misclassified	No
Message-id	<1228470134.48.0.581674090782.issue1215@psf.upfronthosting.co.za>
In-reply-to

Content
The docs already say "Because the C signal handler always returns, it makes little sense to catch synchronous errors like :const:`SIGFPE` or :const:`SIGSEGV`." Should this still be reworded or promoted to a warning?

The docs already say 
"Because the C signal handler always returns, it makes little sense to
catch synchronous errors like :const:`SIGFPE` or :const:`SIGSEGV`."

Should this still be reworded or promoted to a warning?

History
Date	User	Action	Args
2008-12-05 09:42:14	georg.brandl	set	recipients: + georg.brandl, gvanrossum, tebeka, Rhamphoryncus, schmir
2008-12-05 09:42:14	georg.brandl	set	messageid: <1228470134.48.0.581674090782.issue1215@psf.upfronthosting.co.za>
2008-12-05 09:42:13	georg.brandl	link	issue1215 messages
2008-12-05 09:42:13	georg.brandl	create