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 Anssi.Kääriäinen
Recipients Anssi.Kääriäinen, amaury.forgeotdarc, benjamin.peterson, isoschiz, ncoghlan, vstinner
Date 2013-04-19.13:51:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
True, except GeneratorExit will run at garbage collection time and this will result in reference cycle problems. Checking if there is no except GeneratorExit clause might be too complicated.

I still think this is worth a brief note in the gc docs. The gc docs talk only about __del__ methods, and there isn't one defined for the example generator. The generator does have something technically equivalent, but I don't spot any actual __del__ methods in the reference loop.

A docs mention will not help much in avoiding this problem, but it will at least make the code behaviour equivalent to documentation. A mention in the gc docs would have helped me when trying to debug the leak in Django.
Date User Action Args
2013-04-19 13:51:43Anssi.Kääriäinensetrecipients: + Anssi.Kääriäinen, amaury.forgeotdarc, ncoghlan, vstinner, benjamin.peterson, isoschiz
2013-04-19 13:51:43Anssi.Kääriäinensetmessageid: <>
2013-04-19 13:51:43Anssi.Kääriäinenlinkissue17468 messages
2013-04-19 13:51:43Anssi.Kääriäinencreate