On Tue, Mar 20, 2012 at 6:02 PM, Donald Stufft <donald.stu...@gmail.com> wrote: > So you fix the problem for the people who agree that username should be > longer, and that email > should be longer, but not the people who feel that email should be longer > but username is fine? > > Those settings do not feel any cleaner to me personally than monkey patching > the models. >
The difference is that new projects will have sane defaults for the size of an email address, and support using an email address, or a token that looks like an email address (facebook), as a username. Monkey patching the models is a process that has to be repeated again, and again, and again, and again, and again, and again. So, with all bugs, people tend only to care if it affects you. My company has hundreds of different websites, all of which SSO authenticate against a central site. Most of our newer websites are Django based. Each time we make a site, the DB structure is created that simply cannot handle a good percentage of our users - 18% of them have email addresses that do not fit within the django limits. So, we're not dumb, we can fix this - and we have for all our existing sites. The problem is that when a new site is created, that developer has to explicitly remember to fix the broken django default behaviour. Guess what happens when they do not remember to do it? I get a defect report, which I then have to co-ordinate with the client, co-ordinate with the developer, fix the site, inform the customer. It is most frustrating to have to continue to fix the same bug, over and over again, with no sign that the project responsible for the bug will ever fix the problem. Using a setting pragmatically fixes the problem, but offends people's sensibilities. Even with pluggable auth, the proposal is to leave the stock user model exactly as it is now - ie broken. If using a setting can fix this pragmatically going forward, then why not? Cheers Tom -- 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 django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
