Hi Jacob, On Sunday, March 3, 2013 5:08:24 PM UTC+1, Jacob Kaplan-Moss wrote: > > I actually strongly disagree: I think Django *should* ship an > "authenticate-using-email" system. >
Out of curiosity, since I barely have this need by myself: Is it "authenticate-using-email" or "use-email-as-username". Authentication via Email can be done via a backend easily (though we should make the email column unique then). So I am wondering what the main issue here is: is it having username beeing a required field (an uuidv4 should suffice as a workaround currently) or something different? I can't promise it'd go in -- I'm not going to > overrule a -1 from Florian by fiat -- but I think having a concrete > patch on the table will make it easier to make a decision. No worries, if it would exist it would have been a -0.5; either way, a concrete patch would certainly help. If it does make it into core I'd still prefer the most minimal solution possible. Regarding the current proposal: Luke, can you tell us how your changes would play with the current forms etc? Especially since some forms have a hard coded dependency on a concrete user model (by design). I'd prefer not to duplicate all those forms if somehow possible. Cheers, Florian -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
