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 amaury.forgeotdarc, ideasman42
Date 2009-06-14.22:21:54
SpamBayes Score 5.2301207e-06
Marked as misclassified No
Message-id <1245018116.05.0.897931165803.issue6284@psf.upfronthosting.co.za>
In-reply-to
Content
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?
History
Date User Action Args
2009-06-14 22:21:56amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, ideasman42
2009-06-14 22:21:56amaury.forgeotdarcsetmessageid: <1245018116.05.0.897931165803.issue6284@psf.upfronthosting.co.za>
2009-06-14 22:21:54amaury.forgeotdarclinkissue6284 messages
2009-06-14 22:21:54amaury.forgeotdarccreate