Currently a bidict and its inverse maintain strong references to one another and one a

In the meantime, the garbage collector handles these just fine: <div class="snippe

document current behavior: <a class="commit-link" data-hovercard-type="commit" data-ho

use weakref? about bidict HOT 2 CLOSED

jab commented on August 12, 2024

use weakref?

from bidict.

Comments (2)

jab commented on August 12, 2024

In the meantime, the garbage collector handles these just fine:

~> ipython
Python 2.7.8 (default, Aug 28 2014, 15:56:03)
Type "copyright", "credits" or "license" for more information.

IPython 2.3.0 -- An enhanced Interactive Python.
?         -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help      -> Python's own help system.
object?   -> Details about 'object', use 'object??' for extra details.

In [1]: import gc

In [2]: gc.set_debug(gc.DEBUG_COLLECTABLE | gc.DEBUG_UNCOLLECTABLE | gc.DEBUG_OBJECTS)

In [3]: gc.collect()
...
Out[3]: 211

In [4]: from bidict import bidict

In [5]: b = bidict()

In [6]: b = None

In [7]: gc.collect()
gc: collectable <bidict 0x10cfb57d0>
gc: collectable <dict 0x10cfe3398>
gc: collectable <bidict 0x10cfb5710>
gc: collectable <dict 0x10cfd8280>
Out[7]: 4

This just demonstrated that once a bidict's refcount drops to 0, the garbage collector is able to free it (b), the inverse bidict it refers to and that refers to it (b._inv), and their two backing dicts (b._fwd and b._bwd).

Punting for now.

from bidict.

jab commented on August 12, 2024

document current behavior: 54bece2

from bidict.

Recommend Projects