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 r.david.murray
Recipients barry, brett.cannon, r.david.murray
Date 2013-06-08.02:18:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I'm arguing that the statement is false.  I think that whether or not it should be a weakref in this and the other cases depends on whether you think an exception object should keep an object alive or not.  It is fairly unlikely that a key would get into a cycle with an error message, though certainly not impossible.

The "keep alive" question probably boils down to whether or not we want it to be the case that clearing the traceback attribute releases all the "extra" pointers an exception holds on to, or if it is acceptable that an arbitrary number of additional attributes might do so.

I'm inclined to think that using weakrefs would make using the attributes more complicated for relatively little gain.
Date User Action Args
2013-06-08 02:18:37r.david.murraysetrecipients: + r.david.murray, barry, brett.cannon
2013-06-08 02:18:37r.david.murraysetmessageid: <>
2013-06-08 02:18:37r.david.murraylinkissue18163 messages
2013-06-08 02:18:36r.david.murraycreate