Message157733
| Author |
kristjan.jonsson |
| Recipients |
Jim.Jewett, Yury.Selivanov, asvetlov, ebfe, jimjjewett, kristjan.jonsson, lehmannro, michael.foord, pitrou, stutzbach |
| Date |
2012年04月07日.13:00:07 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1333803609.82.0.595191178481.issue10576@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Here is an updated patch, taking Jim's and Antoine's comments into account.
Jim, I ́d like to comment that I think the reason __del__ objects are uncollectable is more subtle than there being no defined order of calling the __del__ functions. More significantly, no python code may be executed during an implicit garbage collection.
Now, it is possible that one could clean up cycles containing only one __del__ method during _expcicit_ collections (calling gc.collect()) but it hardly seems worth the effort. |
|