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
22203	"Automatically get default value for ""current_app"", for easier namespace support."	Tai Lee	nobody	"Right now it seems that for a generic app to support the possibility of being installed in a URLconf with a namespace, the app author will need to take care to explicitly define a `current_app` for every call to `reverse()`, `TemplateResponse`, `RequestContext`, `Context` and `{% url %}`.

Django already adds a `ResolverMatch` object to every request. Shouldn't Django just use this to get a default value for ""current_app"", whenever users don't explicitly define one?

This should make it almost a non-issue to define the current app for every case except explicit calls to `reverse()`, `Context` and templates that are rendered without a `RequestContext` object (as none of these have access to the request).

We could even get a sensible default in those cases as well by storing the current app in thread local storage, and using that as a default in `reverse()`.

Any objections, or any reason why Django doesn't already or can't do this?
"	Uncategorized	closed	Core (URLs)	dev	Normal	wontfix			Unreviewed	0	0	0	0	0	0