Weakrefs to classes that derive from str
rNOSPAMon at flownet.com
Thu Mar 31 03:47:35 CEST 2005
In article <RbB2e.52616$u76.11019 at trndny08>,
"Raymond Hettinger" <vze4rx4y at verizon.net> wrote:
> [Ron Garret]
> > Why doesn't this work?
> > >>> from weakref import ref
> > >>> class C(str): pass
> > ...
> > >>> ref(C())
> > Traceback (most recent call last):
> > File "<stdin>", line 1, in ?
> > TypeError: cannot create weak reference to 'C' object
> . . .
> > Everything but strs.
> Also subclasses of tuple are not weak referencable.
> The issue is in the design of the C structure as a variable-sized immutable
> object. Both strings and tuples allocate as a single unit of memory that
> both the header information and the content information (the characters in a
> string or the array of object pointers for a tuple). Since the size varies
> one string or tuple to the next, there is no straight-forward way for a
> to add an additional header field pointing to a list of weak references.
> For lists and dicts, this is not a problem because the object is allocated in
> two sections, a fixed size header component and a pointer to another area of
> memory to hold the contents of the collection. This makes it possible for a
> subclass to graft-on a weak reference pointer at a known, fixed offset from
> beginning of the header.
> There are two ways to fix this. One is to add a weak reference pointer to
> string object -- that way you wouldn't even have to subclass it. Another way
> to break the object into two pieces as is done for mutable containers like
> and lists.
> Both approaches consume time and space. In general, that is not a big deal,
> fast, memory efficient strings and tuples are at the center of all things
> Python. The need to weak reference this objects is somewhat rare in
> to the frequency of their other uses. It did not make sense to always pay a
> time/space penalty just to create the possibility of weak referencing.
> While the design decision is unlikely to change, the docs could certainly be
> improved. A doc patch would be welcome.
> FWIW, the work-arounds are to weak-reference instances of UserString or to
> create a custom class with a has-a relationship instead of an is-a
Thanks for the detailed explanation. I understand now why you can't
create weakrefs to these types. What I don't understand still is why
you can't create weakrefs to user-defined classes that inherit from
these types. I would think that instances of user-defined classes have
the same header structure regardless of what they inherit from. This
would seem to be supported by the fact that you can create weakrefs to
instances of user-defined classes that inherit from int and float.
More information about the Python-list