All of the following documented views are:
Bases: django.views.generic.base.TemplateView
A view to confirm an email address change request.
An instance of EmailChange, if found.
The template used to render this view.
If an EmailChange object that has been created by the user is not found, the user will be redirected to EmailChangeCreateView.
Inserts following variables into the context:
Saves the new email address to django.contrib.auth.models.User and send a email_change_confirmed signal.
Bases: django.views.generic.edit.CreateView
A view to create an EmailChange object.
alias of EmailChangeForm
alias of EmailChange
If an EmailChange object that has been created by the user is found, the user will be redirected to EmailChangeDetailView.
Saves the email address change request, sends an email to confirm the request, adds a success message for the user and redirects to EmailChangeDetailView.
Bases: django.views.generic.edit.DeleteView
A view to delete an EmailChange object.
alias of EmailChange
If an EmailChange object that has been created by the user is not found, the user will be redirected to EmailChangeCreateView.
Returns the URL to redirect to after an email address change request has been deleted by an user. The URL to redirect to can be customized by setting EMAIL_CHANGE_DELETE_SUCCESS_REDIRECT_URL.
Bases: django.views.generic.detail.DetailView
A view to display an EmailChange object.
alias of EmailChange
If an EmailChange object that has been created by the user is not found, the user will be redirected to EmailChangeCreateView.
Bases: django.views.generic.base.RedirectView
A view to redirect users to other views.
Determines that this view will always issue a HTTP 307 (Temporary Redirect) status code.
If an EmailChange object is found that has been created by the user, the user will be redirected to EmailChangeDetailView. If such an object is not found the user will be redirected to EmailChangeCreateView.