[issue24743] Make _PyTraceback_Add public

Irit Katriel added the comment: This seems like something that needs to be discussed on python-ideas before it can be brought to implementation. -- resolution: -> rejected stage: needs patch -> resolved status: open -> closed ___ Python tracker <

[issue24743] Make _PyTraceback_Add public

Irit Katriel added the comment: The information about the location in c++ where the error occurred can be included in the exception message. I don't think adding fake frames to the traceback is a pattern that we should support through a public API. -- nosy: +iritkatriel ___

[issue24743] Make _PyTraceback_Add public

Serhiy Storchaka added the comment: It looks like a hack and is used only three time in the CPython code. What is your use case? How do you use it? -- ___ Python tracker ___

[issue24743] Make _PyTraceback_Add public

Change by SilentGhost : -- nosy: +serhiy.storchaka versions: -Python 3.7 ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue24743] Make _PyTraceback_Add public

Change by Cheryl Sabella : -- stage: -> needs patch versions: +Python 3.7, Python 3.8 -Python 3.4, Python 3.5, Python 3.6 ___ Python tracker ___ __

[issue24743] Make _PyTraceback_Add public

New submission from Michael Ensslin: Python 3.4.3 introduced an internal function, _PyTraceback_Add, which is quite useful when constructing Python exception objects. I'm using it when constructing a Python Exception object from a C++ exception object, to add "fake traceback frames" that conta