A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2001-November/018659.html below:

[Python-Dev] gc.garbage

[Python-Dev] gc.garbage [Python-Dev] gc.garbageTim Peters tim.one@home.com
Sat, 17 Nov 2001 16:06:48 -0500
I notice the gc docs say:

    The following variable is provided for read-only access:
                                           ^^^^^^^^^^^^^^^^
    garbage
        A list of objects which the collector found to be unreachable ...

This isn't clear to me.  When I find finalizer cycles in gc.trash, I want to
clean them up by breaking the cycles.  Unless I remove the instances from
gc.trash too, their appearance in that list keeps them alive despite that
the cycles are broken.  But "read-only access" seems to imply "don't
mutate", and I don't believe that was intended.  True?  False?




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