[Python-Dev] once enabled gc won't go away until explicitly disabled?

Barry A. Warsaw bwarsaw@beopen.com
Tue, 11 Jul 2000 11:38:55 -0400 (EDT)

>>>>> "SM" == Skip Montanaro <skip@mojam.com> writes:

    SM> I had been running with --with-cycle-gc, then the mystery bug
    SM> hit yesterday, so last night I was working on other stuff and
    SM> wanted to disable it.  I tried removing config.cache and then
    SM> executing configure as

    SM>     ./configure --with-threads

    SM> but gc was still there.  Then I explicitly commented out the
    SM> gc line in Modules/Setup.config.  Still no luck.  Finally, I
    SM> configured as

    SM>     ./configure --with-threads --without-cycle-gc

    SM> and then it went away.

    SM> Is this the correct behavior?

Yes, although both gc and threads are enabled by default in the
current betas (so you don't need --with-threads).  Whether they'll be
enabled for the final release is still TBD.