New submission from Antoine Pitrou <pit...@free.fr>: I haven't verified this through any test (actually I'm wondering how to deterministically reproduce it), but logically there are cases where gc.collect() (and, similarly, PyGC_Collect()) won't work as advertised.
Specifically, when the GC is asked to collect a given generation but a younger generation is already being collected, collect() will simply notice this and return 0. However, only the younger generation will have been collected, not the generation asked by the user. It wouldn't take too much effort to make gc.collect() and PyGC_Collect() truely deterministic. ---------- messages: 79673 nosy: pitrou priority: normal severity: normal stage: test needed status: open title: gc.collect() won't always collect as expected type: behavior versions: Python 2.6, Python 2.7, Python 3.0, Python 3.1 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue4924> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
