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

[Fred L. Drake, Jr.]

Tim Peters writes:
 > For example, create a new-style class and you've created cycles.
 > If you have a customer who disables cyclic GC, they'll have to
 > avoid other newer features too, or endure leaks.

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.


  -Fred

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