Malcolm Tredinnick fc26da645a Add warning when using cache keys that might not work with memcached. ... This means testing with local dev caches (not memcache) will warn developers if they are introducing inadvertent importabilities. There is also the ability to silence the warning if a dev is not planning to use memcache and knows what they are doing with their keys. Thanks to Carl Meyer for the patch. Fixed #6447. git-svn-id: http://code.djangoproject.com/svn/django/trunk@13766 bcc190cf-cafb-0310-a4f2-bffc1f526a37		2010-09-12 18:45:26 +00:00
..
__init__.py	Refactored cache from django/core/cache.py into django/core/cache package, with each backend getting a separate module. This keeps things cleaner and uses less memory, because the backend module is only loaded if it's needed.	2006-02-24 06:07:01 +00:00
base.py	Add warning when using cache keys that might not work with memcached.	2010-09-12 18:45:26 +00:00
db.py	Add warning when using cache keys that might not work with memcached.	2010-09-12 18:45:26 +00:00
dummy.py	Add warning when using cache keys that might not work with memcached.	2010-09-12 18:45:26 +00:00
filebased.py	Add warning when using cache keys that might not work with memcached.	2010-09-12 18:45:26 +00:00
locmem.py	Add warning when using cache keys that might not work with memcached.	2010-09-12 18:45:26 +00:00
memcached.py	Fixed #12427 -- Started the deprecation path for cmemcache support. Thanks to otherjacob for his work on this issue.	2010-03-10 14:02:59 +00:00