[Python-Dev] Death to WITH_CYCLE_GC

Tim Peters tim.one@comcast.net
Tue, 02 Jul 2002 22:10:36 -0400


I don't consider cyclic gc to be an experiment anymore.  It's proved to be
very solid code, and it hasn't become orphaned either <wink>.

What say ye to nuking the #ifdefs conditionalizing it in the core for 2.3?
They're irritating, the code base without cyclic gc is never tested, the
touchy trashcan mechanism works in a radically different way when cyclic gc
isn't compiled in, and if cyclic gc is compiled in it's easy to turn it off
at will (gc.disable()).  It does cost memory for the gc header on
containers, but since we never test without it the ability to compile it out
isn't much of "a feature".

+1 from me <ahem>.