[Python-ideas] feature to make traceback objects usable without references to frame locals and globals

Nick Coghlan ncoghlan at gmail.com
Mon Jun 28 14:10:09 CEST 2010

On Mon, Jun 28, 2010 at 9:31 PM, M.-A. Lemburg <mal at egenix.com> wrote:
> Nick Coghlan wrote:
>> When Python code calls into Pyrex/C code which then call back into
>> Python, I understand they insert dummy frames into the tracebacks to
>> make the call stack more complete.
> Thanks for that bit of information. I suppose they do this for
> better error reporting, right ?

I believe so, but keep in mind that I've never actually used them
myself, I've just seen this behaviour described elsewhere.

It makes sense for them to do it though, since following a call stack
through a plain C or C++ extension module can get rather confusing at


Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

More information about the Python-ideas mailing list