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
23762	CACHE_MIDDLEWARE_ANONYMOUS_ONLY deprecation period was only partial	Keryn Knight	Kenneth Kam	"As far as I can tell, the standard 2-versions deprecation policy was only partially implemented for the `CACHE_MIDDLEWARE_ANONYMOUS_ONLY` setting, because as of Django 1.7.1, the deprecation warning is only applied to [https://github.com/django/django/blob/c5780adeecfbd85a80b5aa7130dd86e78b23e497/django/middleware/cache.py#L167 CacheMiddleware], which is in contrast to how the documentation has [https://github.com/django/django/blob/c5780adeecfbd85a80b5aa7130dd86e78b23e497/docs/topics/cache.txt#L437 recommended using the two partial Middlewares] for a long time, due to the way MIDDLEWARE_CLASSES is applied in different orders depending on the point in the request/response cycle.

As it's already gone in 1.8, the best course of action would be improve the [https://docs.djangoproject.com/en/dev/internals/deprecation/#deprecation-removed-in-1-8 deprecation notes for 1.8] in a way that really calls attention to this omission (rather than the one-line bullet point it currently receieves), as well as add some sort of notification to [https://docs.djangoproject.com/en/dev/releases/1.8/ the release notes], lest it be missed - failure to do so would lead to many people wondering why the setting doesn't work anymore [for which the answer needs to be ""read #15201""]

Meanwhile, while asking about making this ticket vs. re-opening #15201 in #django-dev, MarkusH suggested that the [https://github.com/django/django/blob/c5780adeecfbd85a80b5aa7130dd86e78b23e497/django/middleware/cache.py#L206 stack level for the warning should be 2, not 1].

Marking as master (current 1.8) for the purposes of updating the documentation, though the missing warning can only apply as far as 1.7"	Bug	closed	Documentation	dev	Normal	fixed		django@…	Accepted	1	0	0	0	1	0