Automatically transition away from older memcached backends.

Review Request #6481 — Created Oct. 21, 2014 and submitted

Information

Djblets
release-0.8.x
b094987...

Reviewers

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

reviewbotreviewbot
reviewbot
  1. 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
    
    
  2. djblets/siteconfig/tests.py (Diff revision 1)
     
     
    Show all issues
     redefinition of unused 'test_cache_backend_with_caches' from line 150
    
  3. 
      
chipx86
reviewbot
  1. Tool: Pyflakes
    Processed Files:
        djblets/cache/backend_compat.py
        djblets/siteconfig/tests.py
    
    
    
    Tool: PEP8 Style Checker
    Processed Files:
        djblets/cache/backend_compat.py
        djblets/siteconfig/tests.py
    
    
  2. 
      
david
  1. Ship It!

  2. 
      
chipx86
Review request changed
Status:
Completed
Change Summary:
Pushed to release-0.8.x (e8e6c43)