On Tue, 2009-04-07 at 10:16 -0700, pkenjora wrote: > Hi, > > Why not remove the '@' filter and allow the specific project > developer the freedom to use email as username? What was the > reasoning behind this?
One reason is that usernames can be made to be unique, since you're selecting a new username and if the one you choose is already taken, you can choose another one. You cannot, however, easily change your email address and there are cases of different people sharing a single email address or the same person needing/wanting to create multiple accounts. Another reason is likely simply historical; usernames that *aren't* email addresses are much more readable and traditional in social-based sites and that was what was used in the initial implementation. The uniqueness problem mentioned above is very real, however, so Django is protecting people from doing dumb things here. If you want to work around that, it's possible and fairly easy, but not heavily advisable. > I always like Django because it didn't try to force development down > a specific path. All developers have their own way and every project > is unique, for a long time Django accommodated that. I'm a bit > worried about where this is going... It's not "going" anywhere. The username requirements have been the same since the very first day you used Django. Don't frame this as something slipping out of control, please. > > I'm worried that the workarounds just introduce unnecessary > complexity. Almost as if you shouldn't workaround a valid constraint, isn't it? :-) Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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 -~----------~----~----~----~------~----~------~--~---
