Amaury Forgeot d'Arc <amaur...@gmail.com> added the comment: PyErr_Print seems a too high-level function for this usage: - it uses sys.excepthook - it exits the process if the exception is SystemExit (!)
I'd prefer a function similar to PyErr_Display. And sys.stderr should not be redirected to a temporary stream: this change is not thread safe. For example, A new function PyErr_DisplayEx could take an additional (PyObject *fp) argument. As for the Blender use case: isn't it appropriate for Blender to change sys.stderr globally, since the console is not used? ---------- nosy: +amaury.forgeotdarc _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6284> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
