To me, it boils down to something quite simple. Django's built-in auth system uses usernames for identifying users, and email addresses as a way to communicate with those users.
Yes, it might well be better for some sites to use email addresses as the username, but in those cases, you would want it to be just that: email addresses *as* usernames. You wouldn't want separate usernames at all. So, like many other things these days, it comes down to a bikeshed. The Django authors built theirs the way they'd like it built, because it's what they needed for what they were doing. If you need your own, you're more than welcome to build your own, possibly using theirs as a base. But it seems pretty senseless to be discussing which way should the official distribution should be done, since it's pretty obvious that the way it will be done is the way it's already being done. -Gul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
