What no one is discussing here is is that django-registration is just one out of several popular authentication backends that match it for use and great exceed it's functionality. They include:
* django-allauth * django-userena * python-social-auth (nee django-social-auth) These three projects are extremely well maintained (huge communities of supporters), support dozens of OAuth implementations, and are the modern cornerstone of current Django registration. Bugs are fixed quickly, updates for OAuth providers come frequently, and **just plain work without forking**. django-allauth in particular not only easily mirrors django-registration core functiomality, it has a safer logout mechanism. Why do I bring this up? Well, if Django is going to have a built-in registration system, then I think it should benefit from having more eyes on the problem. While James Bennett is an awesome coder whose work has been a foundation of my own, his solitary effort (https://www.djangopackages.com/packages/p/django-registration/ shows only one committer) simply doesn't compare to the legions of people who have contributed to these other packages. Therefore, I submit that if a registration package will be brought into django.contrib, it should be one of these alternatives. That said, I don't like the idea of adding more functionality to Django, even within django.contrib. IMO, a better alternative would be to suggest registration packages in the documentation of django.contrib.auth. --Daniel Greenfeld On Friday, August 1, 2014 9:17:30 AM UTC-7, Collin Anderson wrote: > > It seems to me, in any case, the first step is to get django-registration > actively maintained again. James Bennett is welcoming proposals of people > to take over maintenance of the project. Get it working well with custom > user models and with python 3. Once django-registration is a thriving app > as popular as django-south (about 10x as many people using it), it would > make sense to think about the possibility of adding it to contrib. > > I think LDAP and oauth (facebook login) support out of the box in django > would be great, though I think it's easier said than done, and > django-registration doesn't even do it out of the box. > > As for me personally. I use the admin in every one of the 18 django > websites I maintain, and in the few websites where non-staff users login to > the website, including this line in urls.py goes a long way for me: > > url(r'^accounts/', include('django.contrib.auth.urls')), > > If email-verification is required, I re-use the password reset code to > handle the tokens. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/f5813b1d-529a-45b2-b14a-b4a78cf99757%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
