Django-registration 1.0 is out(pypi.python.org)
pypi.python.org
Django-registration 1.0 is out
https://pypi.python.org/pypi/django-registration
19 comments
Isn't the documentation actually for 0.8?
Yep, for some reason they decided it would be ok to delay release and deny pull requests for so much time that many people (myself included) simply wrote their own implementations.
Am I missing something, or is there a reason that the Django 1.5 implementation didn't stretch into other parts of the project, like the built-in RegistrationForm? It still uses the old User model directly.
https://bitbucket.org/ubernostrum/django-registration/src/8f...
https://bitbucket.org/ubernostrum/django-registration/src/8f...
Django registration is awesome but still no default templates ( or official companion project that provides them) I don't get it.
The main developer James Bennett has discussed his reasons several times on multiple venues, but the FAQ in the Read the Docs for django-registration gives details in "Does django-registration come with any sample templates I can use right away?"
https://django-registration.readthedocs.org/en/latest/faq.ht...
Other people have provided good baselines to work from, the Djen of Django provides explanations with their samples:
http://agiliq.com/books/djenofdjango/chapter5.html#reusable-...
(note I haven't upgraded to 1.0 so not sure if there are any incompatibilities)
https://django-registration.readthedocs.org/en/latest/faq.ht...
Other people have provided good baselines to work from, the Djen of Django provides explanations with their samples:
http://agiliq.com/books/djenofdjango/chapter5.html#reusable-...
(note I haven't upgraded to 1.0 so not sure if there are any incompatibilities)
Yes.. I have read the faq but
1 "Providing default templates with an application is generally hard to impossible" not true since the introducton of app template loader
2 "A number of things in django-registration depend on the specific registration backend" 99 % uses standard db/user built in backend. If you use social-auth or similar you (almost ) do not need registration
I second 'yourcelf' comment below.. I always use his template as a starting point.
May be a management commas that generate those default templates? ( not a big fan of template generation anyway)
1 "Providing default templates with an application is generally hard to impossible" not true since the introducton of app template loader
2 "A number of things in django-registration depend on the specific registration backend" 99 % uses standard db/user built in backend. If you use social-auth or similar you (almost ) do not need registration
I second 'yourcelf' comment below.. I always use his template as a starting point.
May be a management commas that generate those default templates? ( not a big fan of template generation anyway)
I've used Django Registration on at least 5 projects, and despite having built a good set of templates with the first project, haven't ever been able to reuse them completely.
Registration is (or at least, probably ought to be) a very personal set of decisions for any app/project. I agree that there could be some easily packaged, cookie-cutter defaults, but having experienced all the reasons James Bennett cited for not packaging any templates, I have to say that he's not crazy for their omission.
Registration is (or at least, probably ought to be) a very personal set of decisions for any app/project. I agree that there could be some easily packaged, cookie-cutter defaults, but having experienced all the reasons James Bennett cited for not packaging any templates, I have to say that he's not crazy for their omission.
Here's a set of default templates I wrote. I respect the reasoning for not providing them, but implementing 15 templates to get started out of the box is a bit onerous.
https://github.com/yourcelf/django-registration-defaults
if you want sth more complete, try django-userena.
For the interested, overview of the user registration apps for Django: https://speakerdeck.com/tedtieken/signing-up-and-signing-in-...
Django newbie here, how does Django-registrations compare to django-userena?
From my quick stint with django-userena, it felt very constrained. At that time, my application's login requirements were simple, but needed a few minor tweaks. It's been a while, but I recall that doing so didn't seem like an easy task, so I switched to django-registration then eventually using the Django 1.5 custom user model.
Overall, I'd say do a quick run through of both. If one of them has exactly what you need, stick with it. Otherwise, you are probably better off using the default User model or extending the default.
Overall, I'd say do a quick run through of both. If one of them has exactly what you need, stick with it. Otherwise, you are probably better off using the default User model or extending the default.
Is it now possible (and straightforward) to drop the requirement for a username and solely use email addresses for user accounts?
Why not just enforce the username field to email syntax?
because prior to the new User implementation in 1.5, you couldn't change the length of the username CharField. Long emails wouldn't fit.
I wanted to link to the changelog, but James (Ubernostrum), understandably, hasn't updated it yet.
Note: The documentation[1] still describes 0.9 version.
[1]: https://django-registration.readthedocs.org/en/latest/