Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2000-July/006085.html below:

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

• Previous message: [Python-Dev] once enabled gc won't go away until explicitly disabled?
• Next message: [Python-Dev] once enabled gc won't go away until explicitly disabled?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

>>>>> "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.

-Barry

• Previous message: [Python-Dev] once enabled gc won't go away until explicitly disabled?
• Next message: [Python-Dev] once enabled gc won't go away until explicitly disabled?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4