I agree that it is time for django to change it (at least making the changes easier).
On my project I did create a new user model that inherit from AbstractUser class UserManager(BaseUserManager): ... class User(AbstractBaseUser): email = models.EmailField(unique=True) objects = UserManager() USERNAME_FIELD = 'email' I didn't have an password field because I use a third party(google identity toolkit to authenticate) but you can have one. Here is the full models if you want a sample <https://github.com/kaisaf/gearcircles/blob/master/gc_project/users/models.py> . On Wednesday, November 4, 2015 at 3:36:57 AM UTC-5, Patrick Breitenbach wrote: > > Is there a current "best" approach or module for signup/login with an > email address? > > <rant>I can't believe this is not included with django. In fact, it should > be the default. 80-99% of services and projects do not use usernames.</rant> > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/cc19c134-607d-4f11-af53-cb3f66a2bc40%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
