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

Guido van Rossum guido@python.org
Wed, 05 Feb 2003 11:49:16 -0500

> So desirable or not, re-adding --without-cycle-gc may be hard.

I don't think so. When I read the latest CVS version, I also stumbled on the new-born relationship between trashcan and GC, but forgot to complain about it. My original implementation abused the obtype field of the objects, which looked insane for some developers. But insane or not, I really dislike that for sanity, GC is no longer an option. I know of many companies (all my Stackless customers, for instance), who would never switch to a Python version that needs the GC.

You can help by volunteering to maintain the code that is needed for making GC optional.

--Guido van Rossum (home page: http://www.python.org/~guido/)