Django's memcache backend treats a timeout=0 as invalid and falls back to using a default timeout value:
We previously used the django-cache-machine backend which fixes this:
Could we do something similar in this backend, so timeout=0 are treated as infinite?
Sorry for the late answer - I just noticed your message
Sure we could do this - will work on a patch
make sure the timeout=0 case is not broken - fixes #1