@Anon - Python's memory manager is a garbage colle...

2009-11-15T12:34:25.722-05:00

@Anon - Python's memory manager is a garbage collector that works by tracking the number of references to an object ("reference counting"). When objects have no more external references (nothing uses them), they become candidates to be deleted to regain memory. If two or more objects form a reference cycle (A->B->C->A) then none of the objects will ever have 0 references and they will not be deleted.

In this specific case, the frame active in the exception handler would form a circular reference with the traceback, and so neither would ever be deleted.

This example avoids introducing a circular referen...

2009-11-09T02:46:58.257-05:00

This example avoids introducing a circular reference between the traceback and a local variable in the current frame by ignoring that part of the return value from exc_info(). If you do need the traceback for some reason (such as to log it), you should explicitly delete the local variable when you’re done (using del) to avoid cycles.

Can you please explain this in more detail ? I am a relatively new. Thanks.

Comments on Doug Hellmann: PyMOTW: sys, Part 4: Exception Handling

@Anon - Python's memory manager is a garbage colle...

This example avoids introducing a circular referen...