Opened 8 years ago

Closed 8 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: UI/UX:


I was trying to get memcached working without having the memcached module from 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/", line 475, in ?

cache = get_cache(CACHE_BACKEND)

File "/usr/lib/python2.4/site-packages/django/core/", 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, but it would be nice if Django's fallback class would work. Or at least warn people that it is not working.

Attachments (0)

Change History (1)

comment:1 Changed 8 years ago by adrian

  • Resolution set to fixed
  • Status changed from new to closed

I believe this was fixed in [2378]. Please reopen if it's still a problem.

Add Comment

Modify Ticket

Change Properties
<Author field>
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.