RetroSearch Browse

Wed May 4 16:58:54 CEST 2005 · https://mail.python.org/pipermail/python-dev/2005-May/053304.html

On Wed, 2005-05-04 at 09:46 +0000, M.Utku K. wrote:
> The reinit. issue: The old way of returning old callback when a new 
> callback is set sounds OK. Or better way: there may be an array to hold all 
> the callbacks, Py_FatalError iterates and call each.

Why should reinitialization be allowed at all? Seems to me that this
feature should be exclusively reserved for an embedding application to
handle the fatal in an application specific way; ie ereport(FATAL,()) in
PostgreSQL, which quickly exits after some cleanup. Why should an
extension module be allowed to set this, or reset it?
-- 
Regards, James William Pye

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2005-May/053304.html below:

[Python-Dev] Need to hook Py_FatalError