Automatically transition away from older memcached backends.
Review Request #6481 — Created Oct. 21, 2014 and submitted
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.
| Description | From | Last Updated |
|---|---|---|
|
redefinition of unused 'test_cache_backend_with_caches' from line 150 |
 reviewbot
|
- Change Summary:
-
Fix unit tests.
- Commit:
-
7965bac9e9f2f86f8346b5c23ebbeb88deca32e2b094987734a0044e33ee5ac06732310cf53acbdc
Tool: PEP8 Style Checker Processed Files: djblets/cache/backend_compat.py djblets/siteconfig/tests.py Tool: Pyflakes Processed Files: djblets/cache/backend_compat.py djblets/siteconfig/tests.py