On Jul 2, 8:48 am, "Paul Kenjora" <[EMAIL PROTECTED]> wrote: > I've been using Django for a while and recently started contributing to the > trunk. Previously I ran my own branch but sooner or later that gets > tiresome. So I created a ticket the other day: > > http://code.djangoproject.com/ticket/7591 > > The ticket suggests a patch to contrib/auth that will allow authenticate by > email as well as username. The idea was shot down rather quickly without > any particularly good reason. In order for me to continue contributing to > the trunk I'd like to get in line with the thought processes on Django > development. Could someone here please elaborate on why ticket 7591 is a > bad idea? Or better yet why its a worse idea than other approaches?
It's almost absurdly easy to write your own authentication backend including one that supports authentication through email addresses. See [1] and [2]. The particular axe that I'm grinding lately is for Ticket 3011 [3], which would allow for a pluggable user model. Perhaps that's more what you're looking for? [1] http://www.djangosnippets.org/snippets/74/ [2] http://www.djangoproject.com/documentation/authentication/#other-authentication-sources [3] http://code.djangoproject.com/ticket/3011 --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
