[issue1195571] simple callback system for Py_FatalError

[Jonathan McDougall]

Jonathan McDougall added the comment:

The latest patch does not allow changing the default behaviour of
aborting the process, which is for me a problem. I am both embedding
and extending python using Boost.Python, but scripting is optional. In
case python fails to initialize, I want to disable scripting but keep
the program running.

Libraries shouldn't abort; they should report errors to the caller and
let it figure out what to do.

--
nosy: +jonathanmcdougall

___
Python tracker 
<http://bugs.python.org/issue1195571>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1195571] simple callback system for Py_FatalError

[Jonathan McDougall]

Jonathan McDougall added the comment:

While trying to come up with a patch, I'm starting to realize the number
of modifications needed to make this work. Py_FatalError() is called all
over the place assuming that it never returns. The scope of this feature
is enormous.

I'm wondering what would happen if I threw an exception from there :)

--

___
Python tracker 
<http://bugs.python.org/issue1195571>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com