j: Next unread message
k: Previous unread message
j a: Jump to all threads
j l: Jump to MailingList overview
Nick Coghlan wrote:
On Sun, Jun 27, 2010 at 7:53 AM, M.-A. Lemburg firstname.lastname@example.org wrote:
He's not talking about creating traceback objects outside the core, but being able to reuse tracebacks created by the core without keeping alive a whole chain of objects.
With the question I was referring to the suggestion by Greg Ewing in which he seemed to imply that Pyrex and Cython create traceback objects.
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 ?
-- Marc-Andre Lemburg eGenix.com
Professional Python Services directly from the Source (#1, Jun 28 2010)
::: Try our new mxODBC.Connect Python Database Interface for free ! ::::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/