15 Jan
2009
15 Jan
'09
8:26 a.m.
Campbell Barton wrote:
recently I have been experimenting with a new api for blender3d, one of the things it needs to be able to do is give python errors (tracebacks) to our own error reporting api.
The problem is that Python/C api has no way to get the text that PyErr_Print() prints, as a string. [...]
- Use pythons traceback module from C (this isnt so bad, but Id prefer not to have core parts of our api relying on *.py modules)
I'd opt for not fixing problems before they clearly turn out to be problems, and just go with the traceback module. You only use it for debugging the unexpected failure case after all, so this isn't performance critical or anything.
Stefan