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

[Tim Peters]

[Christian Tismer]
> ...
> I know of many companies (all my Stackless customers, for
> instance), who would *never* switch to a Python version that
> needs the GC.

What relationship does Stackless have with user code creating cycles among
Python objects?  I don't see any.

One thing getting overlooked here is how many newer C-level Python objects
register with GC, due to that so many new features end up creating reference
cycles.  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.