On Thu, May 5, 2011 at 9:08 AM, Yishai Beeri <yis...@platonix.com> wrote: > Wouldn't it be possible to work around this, even for the time being, by > having auth.User read a SETTING to use as the default max_length (defaulting > of course to the old 75)?
No, for any number of reasons. Primary because if you get it wrong Django will explode in your face. Settings that cause crashes when set incorrectly aren't acceptable. There are plenty of other workarounds -- the easiest is to note the email field is optional and just create a RealUserEmail object with a OneToOne to User. Given that, a hacky workaround in Django itself just isn't going to happen. The right thing to do is to get the auth refactor done and solve this and all the other issues at the same time. Jacob -- 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.
