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/041926.html below:

[Python-Dev] Re: Tracebacks into C code

[Python-Dev] Re: Tracebacks into C code [Python-Dev] Re: Tracebacks into C codeEdward C. Jones edcjones at erols.com
Sun Jan 11 14:45:51 EST 2004
*Martin v. Löwis wrote:*

> 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"?
/>
> You need to create frame objects. See Modules/pyexpat.c for an example.

That looks complicated.

> Regards,
> Martin
> 
> P.S. This is OT for python-dev.

I should have directly asked:
Should some traceback-through-C capability be put in the Python API?




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