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 akuchling, ghazel, loewis, r.david.murray, terry.reedy, tim.peters, vstinner
Date 2010-06-26.19:23:31
SpamBayes Score 0.0074132034
Marked as misclassified No
Message-id <>
It is true that your proposed feature would provide a way for a programmer to manually resolve the cycle issue; however, the open issue in the pep is how to do this automatically.

But if you hold on to the traceback reference, you should *expect* all those values to persist, so that shouldn't be "surprising".

I repeat my recommendation that you take this to python-ideas for feedback, and then work on a patch if the feedback is positive.

(By the way, I checked with a twisted developer, and what he wanted was a convenient way to manually create traceback objects.)
Date User Action Args
2010-06-26 19:23:34r.david.murraysetrecipients: + r.david.murray, tim.peters, loewis, akuchling, terry.reedy, vstinner, ghazel
2010-06-26 19:23:33r.david.murraysetmessageid: <>
2010-06-26 19:23:32r.david.murraylinkissue1565525 messages
2010-06-26 19:23:31r.david.murraycreate