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
24126	Consider deprecating the current_app argument of auth views	Aymeric Augustin	lukawoj	"All views defined in `django.contrib.auth.views` have the following structure:

{{{
def view(request, ..., current_app=None, ...):

    ...

    if current_app is not None:
        request.current_app = current_app

    return TemplateResponse(request, template_name, context)
}}}

As of Django 1.8 `current_app` is set on the `request` object. (This is debated but no other concrete proposal has been made at this time.)

For consistency the auth views should require the caller to set it on the `request` instead of passing it in a separate argument.

That would also avoid the risk of conflicts between a `current_app` set on the `request` and another `current_app` passed in argument. Currently the latter overrides the former."	Cleanup/optimization	closed	contrib.auth	dev	Normal	fixed	current_app		Accepted	1	1	0	0	0	0