region.get does not respect object cache

import time
from pprint import pprint

from dogpile.cache.region import make_region

region = make_region().configure("dogpile.cache.memory")

region.get_or_create("foo-key", lambda: "foo-value", expiration_time=2)

time.sleep(1)

result_1 = region.get("foo-key")

# should be hit, ok
pprint(dict(result_1=result_1))

time.sleep(2)

result_2 = region.get("foo-key")

# should be miss, fail
pprint(dict(result_2=result_2))

❯ python yolo.py
{'result_1': 'foo-value'}
{'result_2': 'foo-value'}

I expected something like

❯ python yolo.py
{'result_1': 'foo-value'}
NO_VALIUE

[zzzeek]

result_2 = region.get(“foo-key”)

should be miss, fail

pprint(dict(result_2=result_2))

the value is not expired because you have not specified an expiration time.

call it like this:

result_2 = region.get("foo-key", expiration_time=2) then you get:

{'result_1': 'foo-value'}
{'result_2': <dogpile.cache.api.NoValue object>}

so it would appear I need to add a note to the “expiration_time” argument to get() that this is a per-get expiration time, it is not stored with the object. dogpile doesn’t store per-object expiration times.

❯ python yolo.py {‘result_1’: ‘foo-value’} {‘result_2’: ‘foo-value’}

I expected something like

❯ python yolo.py {‘result_1’: ‘foo-value’} NO_VALIUE

[hugoduncan]

Thanks for taking the time to put together the thorough summary above. What you’ve described sounds like a good approach, but I don’t think we’ll have time to do such a broad update. Look forward to seeing if this gets picked up in the future.