[issue4924] gc.collect() won't always collect as expected

2011-06-26 Thread Terry J. Reedy
Changes by Terry J. Reedy tjre...@udel.edu: -- versions: +Python 3.2, Python 3.3 -Python 3.0, Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4924 ___

[issue4924] gc.collect() won't always collect as expected

2011-06-26 Thread Terry J. Reedy
Changes by Terry J. Reedy tjre...@udel.edu: -- versions: -Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4924 ___ ___ Python-bugs-list

[issue4924] gc.collect() won't always collect as expected

2009-01-12 Thread Antoine Pitrou
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

[issue4924] gc.collect() won't always collect as expected

2009-01-12 Thread Martin v. Löwis
Martin v. Löwis mar...@v.loewis.de added the comment: It should be possible to trigger this by invoking gc.collect in an __del__ implementation of an object that is attached to a cycle. However, I don't think this is an important issue; +0 for resolving this by documenting the status quo