Opened 19 years ago
Closed 19 years ago
#1101 closed defect (fixed)
Memcached: fallback method not working.
| Reported by: | Espen Grindhaug | Owned by: | Jacob |
|---|---|---|---|
| Component: | Core (Cache system) | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I was trying to get memcached working without having the memcached module from ftp://ftp.tummy.com/pub/python-memcached/ installed, that means by using Django's build in memcached client. This is the traceback I got:
{{{>>> from django.core.cache import cache
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "/usr/lib/python2.4/site-packages/django/core/cache.py", line 475, in ?
cache = get_cache(CACHE_BACKEND)
File "/usr/lib/python2.4/site-packages/django/core/cache.py", line 472, in get_cache
return _BACKENDS[scheme](host, params)
TypeError: 'NoneType' object is not callable }}}
It was all fixed by installing the memcached module from tummy.com, but it would be nice if Django's fallback class would work. Or at least warn people that it is not working.
I believe this was fixed in [2378]. Please reopen if it's still a problem.