On Thu, Apr 29, 2010 at 11:08 PM, Russell Keith-Magee < freakboy3...@gmail.com> wrote:
> On Fri, Apr 30, 2010 at 5:03 AM, Felippe Bueno <felippe.bu...@gmail.com> > wrote: > > django-1.2 will support this. > > I'm sorry - what is this based on? There haven't been any substantive > changes to contrib.auth in 1.2. It's not on the official "new > features" list. There have been some discussions about some potential > changes, but a design hasn't even been settled on yet. > Possibly http://code.djangoproject.com/changeset/12634, which I think allows storing an email address in the username field? So perhaps some of the hacks can be avoided, if you adopt the convention having the username field be an email address. Though some special code would be needed to enforce that convention....and there is that other email address field hanging around. So no, not exactly what the original question asked for but maybe a bit better than it used to be. Karen -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
