Message187359
| 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 |
<1366379503.63.0.859016462475.issue17468@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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. |
|