Historically, the memcached backend used the class name 'CacheClass',

which we've been setting and many people have stored. While many

backends in Django do still have their CacheClass equivalent, memcached

does not.
We now fix up the name when normalizing the cache backend, which happens

on site settings load. This guarantees nobody will break.

Accidentally broke my install by having the wrong class set. After this, it

loaded properly and I saw I was using memcached.