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 amaury.forgeotdarc
Recipients Tom.Whittock, amaury.forgeotdarc, georg.brandl, gregory.p.smith, jwp, mutkuk, pitrou, vstinner
Date 2011-06-09.08:08:58
SpamBayes Score 2.347383e-09
Marked as misclassified No
Message-id <1307606939.09.0.115884966256.issue1195571@psf.upfronthosting.co.za>
In-reply-to
Content
Sorry, the documentation in the patch is wrong. It should be: "Cause :cfunc:`Py_FatalError` to invoke the given function before printing to standard error and aborting out of the process."

I don't think it's worth making it more complex.  If the application does not want the default behavior (which is already quite minimal anyway), it can always install a hook that never returns.
History
Date User Action Args
2011-06-09 08:08:59amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, georg.brandl, gregory.p.smith, pitrou, vstinner, mutkuk, jwp, Tom.Whittock
2011-06-09 08:08:59amaury.forgeotdarcsetmessageid: <1307606939.09.0.115884966256.issue1195571@psf.upfronthosting.co.za>
2011-06-09 08:08:58amaury.forgeotdarclinkissue1195571 messages
2011-06-09 08:08:58amaury.forgeotdarccreate