Django-registration doesn't implement its own password change view, it reuses the one included in Django (django.contrib.auth.views.password_change
). It is hooked in through registration.auth_urls
which is included in the default
and simple
registration backends.
By default the view uses django.contrib.auth.forms.PasswordChangeForm
(which can be overridden through the password_change_form
parameter).
When you only reuse the form (which you can do of course, just import the above form in your custom view), you should be aware that you would still be missing the whole view logic. So unless you have a more complex view in mind, you should consider to reuse it and just override the registration/password_change_form.html
and registration/password_change_done.html
templates.