Greg Ewing <greg.ewing <at> canterbury.ac.nz> writes: > > What happens if the program enters a phase where it's not > producing any new cyclic garbage, but is breaking references > among the old objects in such a way that cycles of them > are being left behind? Under this rule, the oldest > generation would never be scanned, so those cycles would > never be collected.
We could introduce a kind of "timing rule" such that there is at least one full collection, say, every minute. While timing is not relevant to memory management, it is relevant to the user behind the keyboard. In any case, I think MvL's suggestion is worth trying. Regards Antoine. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
