[issue30560] Py_SetFatalErrorAbortFunc: Allow embedding program to handle fatal errors

2019-05-27 Thread STINNER Victor
STINNER Victor added the comment: Note: if I misunderstood the issue, please open it ;-) -- ___ Python tracker ___ ___ Python-bugs-

[issue30560] Py_SetFatalErrorAbortFunc: Allow embedding program to handle fatal errors

2019-05-27 Thread STINNER Victor
STINNER Victor added the comment: The issue has been fixed in bpo-36763 with the implementation of the PEP 587. A new API now allow to handle Python initialization error with a new PyStatus structure. By the way, bpo-1195571 was a similar issue. -- nosy: +vstinner resolution: -> fi

[issue30560] Py_SetFatalErrorAbortFunc: Allow embedding program to handle fatal errors

2017-06-03 Thread Thomas Perl
Thomas Perl added the comment: Quick fix for the patch: Of course, the line with abort() needs to be removed before this block: +if (_fatal_error_abort_func != NULL) { +_fatal_error_abort_func(msg); +} else { +abort(); +} --

[issue30560] Py_SetFatalErrorAbortFunc: Allow embedding program to handle fatal errors

2017-06-03 Thread Thomas Perl
New submission from Thomas Perl: In our application that embeds a Python interpreter, we had the issue that certain system configurations (namely, a lone "libpython27.dll" without any standard library) caused silent failures (note that this is using Python 2.7, but Python 3.x would be similarl