[Python-modules-team] Bug#806182: Will fix python-django-registration RCs shortly (Was: Re: Request to join DPMT && python-django-registration)

[James Bennett]

Stephan Sürken wrote:
> Let's see if I got this right:
> 
> django-registration is actually no longer discontinued, and now lives at
> 
> https://github.com/ubernostrum/django-registration
> 
> The (incompatible) *-redux fork lives at
> 
> https://github.com/macropin/django-registration

Yes. django-registration upstream has been revived and the latest
release of it (on PyPI as django-registration 2.0.3) is compatible with
Django 1.7 and 1.8, on any Python version supported by those versions of
Django. It also has a feature or two added.

Probably within a week there will also be django-registration 2.1,
compatible with Django 1.8 and 1.9 and some more new stuff in it.

There is an upgrade guide in django-registration's documentation for
coming from older versions of django-registration (0.8 or 1.0):

https://django-registration.readthedocs.org/en/2.0.3/upgrade.html

My advice, personally, would be to target the current master branch of
django-registration (which will become the 2.1 release very soon).
There's a bugfix related to Django making the email field optional, and
a workaround for a performance bug in the 1.9 release of Django, both of
which are probably worth having (and the one new feature coming in
django-registration 2.1 -- checking usernames against a list of reserved
names -- can be turned off if needed for compatibility).