On Fri, Mar 9, 2012 at 8:13 AM, Florian Apolloner <f.apollo...@gmail.com> wrote: >> Should these things really take five years? What happened to pragmatic? > > > Yes, since no one needs it. Okay no one isn't true, but no one (for true > this time) who needed it stepped up and said "I'll implement it and see that > it ends up in trunk" >
I'm sorry, that completely mis-characterises the situation. Lots of people want this, but every single time this has been brought up since I started using django (1.0), a core dev or BFDL has explicitly ruled it out, saying "we cannot do this, requires schema migration, we'll look at it for the next version". At this point, the discussion is stopped. Once a proposal has the smack down from a BFDL, what point is there trying to get it integrated? The next version comes, has it been addressed? No. Will it be addressed in 1.4? No. Will it be addressed in 1.5? Possibly, but I doubt it. At $JOB we've given up waiting for some trivial changes, and have simply patched django to not have these silly, arbitrary and incorrect requirements¹ on email address and username. We live in the real world, we have to be able to handle email addresses that are of a valid length. We cannot tell a paying customer "I'm sorry, your email address is too long, do you have one under 75 characters?" It's a really invalid position to take, knowing something is broken and incorrect, but not fixing it because 'change is hard'. Cheers Tom ¹ Here is my list of things that are broken with d.c.auth: 1) Length and character restrictions on username field. If I want to use emails address as usernames, or usernames with spaces, the choices made at lawrence.com 3+ years ago should not restrict me. 2) Email address fields must be large enough to hold valid email addresses - that's 254 characters. -- 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.
