A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2004-January/041964.html below:

[Python-Dev] Tracebacks into C code

[Python-Dev] Tracebacks into C code [Python-Dev] Tracebacks into C codePhillip J. Eby pje at telecommunity.com
Mon Jan 12 15:11:59 EST 2004
At 12:10 PM 1/11/04 -0500, Edward C. Jones wrote:
>Suppose:
>    I have a Python extension written in C.
>    "My_Func" is a function in the extension which is visible at the 
> Python level.
>    "My_Func" calls the C function "C_func1".
>    "C_func1" calls the C function "C_func2".
>    "C_func2" raises an exception by calling something like "PyErr_SetString".
>How do I make the Python traceback include "C_func1" and "C_func2"?

Pyrex generates code to do this, at least for C functions that it 
"compiles" from Python code; you might look at its generated C code for 
working examples.


More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4