j: Next unread message
k: Previous unread message
j a: Jump to all threads
j l: Jump to MailingList overview
On Mon, Jun 28, 2010 at 9:31 PM, M.-A. Lemburg email@example.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 times.
-- Nick Coghlan | firstname.lastname@example.org | Brisbane, Australia