In https://github.com/SFTtech/openage/pull/1697 we removed the old method for adding C++ backtraces to Python, since Python's _PyTraceback_Add is no longer part of the public API.
An even older solution that we used before https://github.com/SFTtech/openage/pull/1496 also doesn't work anymore. We should find a better way to propagate backtraces that do not depend on unstable Python features.
Solutions?
We could solve this in several ways:
Print the C++ exception backtrace in the C++ code, then forward the exception to Python and raise a Python exception
Problem Description
In https://github.com/SFTtech/openage/pull/1697 we removed the old method for adding C++ backtraces to Python, since Python's
_PyTraceback_Add
is no longer part of the public API.An even older solution that we used before https://github.com/SFTtech/openage/pull/1496 also doesn't work anymore. We should find a better way to propagate backtraces that do not depend on unstable Python features.
Solutions?
We could solve this in several ways: