[Python-Dev] Python 2.3a1's mandatory use of cyclic GC causes existing applications to fail

Fred L. Drake, Jr. fdrake@acm.org
Wed, 5 Feb 2003 13:53:10 -0500


I wrote:
 > Why would creating new style classes create cycles?  The links between
 > a type and derived types use weak references, which do not rely on the
 > cycle GC support.

Tim Peters writes:
 > >>> def f():
 > ...    class C(object):
 > ...       pass
 > ...
 > [9589 refs]
 > >>> f()
 > [9611 refs]
...
 > >>> import gc
 > [9900 refs]
 > >>> gc.collect()
 > 48
 > [9742 refs]
...
 > Take it from there, but don't forget to come for air once an hour <wink>.

Ugh!  Ok, I guess I've not managed to stay on top of what's going on
in Python land for a while...


  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at acm.org>
PythonLabs at Zope Corporation