On Fri, Mar 1, 2013 at 12:04 PM, Florian Apolloner <[email protected]> wrote: > Doing it outside of Django core if fine, inside core is -0 to -1 from me.
I actually strongly disagree: I think Django *should* ship an "authenticate-using-email" system. It's *SUCH* a common desire, and it's actually fairly tricky to get all the pieces in place to do it right. I just cruised StackOverflow: it's asked a ton, and the answers all have something not-quite-right about them, especially now that 1.5 has shipped. So I'm +1 on including something in core. Luke, do you think you can work up a patch? 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. So if you don't mind doing a bit of "spec work" that'd probably give you us best chances of getting this in. Jacob -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
