id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 15217,Cache setting deprecation warning is too aggressive,Adam Vandenberg,nobody,"http://code.djangoproject.com/browser/django/trunk/django/core/cache/__init__.py#L77 I have Django project with no CACHES or CACHE_FOO settings in my settings.py. So I'm relying entirely on whatever is in the global_settings.py for these values (and CACHES={} here.) The line 77 above says that if CACHES is not true, print a deprecation warning. Thus, since I'm not setting anything up here, and CACHES is false in global_settings.py, I see this deprecation warning any time I run my app-specific unit tests. The ""default settings"" should cause no pending deprecation error to be printed when the project itself isn't setting up any cache settings. ",,closed,Core (Cache system),dev,,fixed,blocker,,Accepted,0,0,0,0,0,0