The 1.0 release of django-registration represents a complete rewrite of the previous codebase, and introduces several new features which greatly enhance the customizability and extensibility of django-registration. Whenever possible, changes were made in ways which preserve backwards compatibility with previous releases, but some changes to existing installations will still be required in order to upgrade to 1.0. This document provides a summary of those changes, and of the new features available in the 1.0 release.
Django version requirement¶
As of 1.0, django-registration requires Django 1.4 or newer; older Django releases may work, but are officially unsupported.
The entire codebase was rewritten for 1.0, switching from function-based views accepting keyword arguments to class-based views with overridable attributes. Whether this affects you will depend on how you were using django-registration previously:
- If you’re upgrading from an older release of django-registration, and if you were using the default setup (i.e., the included default URLconf and no custom URL patterns or custom arguments to views), you do not need to make any changes.
- If you had customized django-registration by writing your own backend, you will now need to implement that backend by subclassing the built-in views and overriding or implementing your customizations appropriately. Much of this is similar to previous backend class implementations, so minimal changes to existing code should be required; the primary change is that the backend classes now are the views, so if you had multiple views (e.g., one for signup and one for activation) your backend will now consist of multiple classes – one class per view – rather than one class total.