Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #10554 > unrolled thread
| Started by | Ian Kelly <ian.g.kelly@gmail.com> |
|---|---|
| First post | 2011-07-29 17:01 -0600 |
| Last post | 2011-07-29 17:01 -0600 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Identical descriptor value, without leaking memory? Ian Kelly <ian.g.kelly@gmail.com> - 2011-07-29 17:01 -0600
| From | Ian Kelly <ian.g.kelly@gmail.com> |
|---|---|
| Date | 2011-07-29 17:01 -0600 |
| Subject | Re: Identical descriptor value, without leaking memory? |
| Message-ID | <mailman.1642.1311980495.1164.python-list@python.org> |
On Mon, Jul 25, 2011 at 11:46 AM, Jack Bates <ms419@freezone.co.uk> wrote:
> How can you get a descriptor to return an identical value, each time
> it's called with the same "instance" - without leaking memory?
class MyDescriptor(object):
def __get__(self, instance, owner):
try:
return instance.__cached_value[self]
except AttributeError:
instance.__cached_value = {self: get_value(instance, owner)}
except KeyError:
instance.__cached_value[self] = get_value(instance, owner)
return instance.__cached_value
class MyClass(object):
my_attribute = MyDescriptor()
Placing the cache on the object instance ensures that it won't outlive
the object, and since the full attribute name will be
_MyDescriptor__cached_value, it's highly unlikely to conflict with an
existing attribute. Keying the value on self is necessary in case the
object has multiple descriptors of the same type.
Back to top | Article view | comp.lang.python
csiph-web