Django-registration-redux

Latest version: v2.13

Safety actively analyzes 688823 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 5 of 6

1.0

(Taken from release-notes.rst in this release)

- The 1.0 release of django-registration represents a complete
rewrite of the previous codebase. For information on upgrading,
consult :ref:`the upgrade guide <upgrade>`.

- The largest overall change is that in place of the monolithic backend
classes and function-based views found in django-registration 0.8, in
1.0 all views are class-based. A "backend" now consists of,
typically, one or two subclasses of :ref:`the built-in base views
<views>`.

- Implementing these as class-based views allows for far simpler
configuration and customization, without the overhead involved in
supporting large numbers of optional keyword arguments to
function-based views, or the need to provide a separate class-based
infrastructure for implementing the logic of registration.

- Notably, this implementation is also completely backwards-compatible
for users of django-registration 0.8 who simply used the recommended
default URLConf for one of the supplied backends; those URLConfs exist
in the same locations, and have been rewritten to point to the
appropriate class-based views with the appropriate options.

0.8

- Backend-based rewrite. See docs/upgrade.rst for details.

- Compatibility through Django 1.4.

0.7

- Project hosting moved from Google Code to Bitbucket, and from a
Subversion repository to Mercurial.

- Added test suite.

- Full Django 1.0 compatibility.

- Registration and activation views now accept an `extra_context`
argument, identical to the way that argument works in Django's
generic views.

- Added a custom management command for cleaning up expired
registrations; you can now run `manage.py cleanupregistration` to
handle this.

- BACKWARDS-INCOMPATIBLE CHANGE: The "username" field in
`RegistrationForm` is now a `RegexField`.

- BACKWARDS-INCOMPATIBLE CHANGE: Removed the standalone script for
deleting expired user registrations; use the new management command
instead.

0.6

- Packaged from revision 166 in Subversion.

- Fixed a multiple-objects exception in
`RegistrationFormUniqueEmail` when multiple users already have the
same email address.

- Changed the `success_url` of the `register()` view to use
reverse URL resolution.

- Added an `extra_context` argument to the `register` and
`activate` views, mimicking its functionality in Django's generic
views.

- BACKWARDS-INCOMPATIBLE CHANGE: Switched the admin declaration to be
compliant with the newforms-admin refactor; the admin declaration
now lives in `registration/admin.py`.

- BACKWARDS-INCOMPATIBLE CHANGE: Switched form imports from using
`django.newforms` to using `django.forms`; the old style now
raises a deprecation warning on Django trunk and on Django 1.0
alpha.

0.5

- Packaged from revision 155 in Subversion.

- Added Serbian translation.

- Added Italian translation.

- Username/email uniqueness checks are now case-insensitive. This is
potentially backwards-incompatible if you relied on them being
case-sensitive, but I don't know of any reason why you'd be doing
that.

- Included forms now use lazy translations.

- The `register` view can now handle files submitted for use in form
processing.

- Reactivation of a manually-deactivated account is now prevented by
changing the activation key, on successful activation, to a dummy
string which will fail on subsequent activation attempts.

Version 0.4p2, 10 Feburary 2008:

- Added Brazilian Portuguese translation.

- Added Japanese translation.

- Added Hebrew translation.

- Minor documentation fixes.

Version 0.4p1, 16 December 2007:

- Packaged from revision 129 in Subversion.

- Added Polish translation.

0.4

- Packaged from revision 122 in Subversion.

- Added Greek translation.

- Added Russian translation.

- Changed `maxlength` to `max_length` now that Django issues a
deprecation warning for it.

- BACKWARDS-INCOMPATIBLE CHANGE: Changed the password validation to be
on `clean()` instead of `clean_password2()`. This means that
errors from this must be accessed via `non_field_errors()`.

Version 0.3p5, 6 October 2007:

- Packaged from revision 112 in Subversion.

- Added German translation.

- Fixed a mismatch between the default `RegistrationForm`'s maximum
length on email addresses and the actual maximum length on Django's
`User` model.

- Fixed a situation where bad input for the `password1` field on
`RegistrationForm` could cause validation of `password2` to fail
with an exception.

Version 0.3p4, 4 October 2007:

- Packaged from revision 101 in Subversion.

- BACKWARDS-INCOMPATIBLE CHANGE: In response to larger numbers of
complaints from people trying to use the example templates as-is,
the example templates have been removed.

Version 0.3p2, 23 September 2007:

- Packaged from revision 100 in Subversion.

- Fixed `activate` view to actually take the `template_name`
argument.

Version 0.3p1, 22 September 2007:

- Packaged from revision 99 in Subversion.

- Fixed a typo in docs/overview.txt.

- Fixed a typo in bin/delete_expired_users.py.

- Added French translation.

Page 5 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.