My django-email-login app ( https://bitbucket.org/tino/django-email-login/overview) does this by putting a hash of the email adress in the username field. It isn't as nice as it could be, but it works.
I would really like to see this solved another way, but it is a hard problem with the current restrictions. Tino On Fri, Mar 9, 2012 at 09:23, Danny Adair <danny.ad...@unfold.co.nz> wrote: > On Fri, Mar 9, 2012 at 21:13, Florian Apolloner <f.apollo...@gmail.com> > wrote: > >[...] > > Yes, since no one needs it. Okay no one isn't true, but no one (for true > > this time) who needed it stepped up and said "I'll implement it and see > that > > it ends up in trunk" > > It's the "required" of username that's the problem if you don't want a > username at all when authenticating against email. > It would have to be not required and check required fields in clean() > where the backend could be asked what's really required. > And there's Mr. Schema Migration again... > > Cheers, > Danny > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-developers@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
