This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pablogsal
Recipients BTaskaya, james, pablogsal, serhiy.storchaka, vstinner, xtreak
Date 2019-10-19.21:28:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> But the problem is that making a reference to the object we can prolong its lifetime and even create a reference loop.

If I'm not mistaken, as long as the traceback is alive, the object is alive beacuse the frames will contain it. The other case is if the exception is not propagated, but in that case it should just die unless explicitly captured. 

The cycle only happens if the object has a reference to the exception, and that should not happen in the general case.
Date User Action Args
2019-10-19 21:28:04pablogsalsetrecipients: + pablogsal, vstinner, serhiy.storchaka, james, xtreak, BTaskaya
2019-10-19 21:28:04pablogsalsetmessageid: <>
2019-10-19 21:28:04pablogsallinkissue38530 messages
2019-10-19 21:28:04pablogsalcreate