It's not just the django.contrib apps you lose, it's any app that uses a ForeignKey to users. Which can be a lot of them.
On Friday, February 17, 2012 at 5:13 AM, Jonathan Slenders wrote: > > On 16 fév, 13:05, Tom Evans <tevans...@googlemail.com > (http://googlemail.com)> wrote: > > 75 isn't large enough these days for either email or username. We run > > a patched version of django for some time that has changed both these > > fields to 255 characters in order to accommodate the needs of our > > users. See RFC 3696. > > > > > This and other issues made us moving away from contrib.auth and > contrib.sessions. It's not too hard to write your own custom > authentication and session middleware, and you can migrate whereever > you want to. The main problem is if you depend on other libraries with > rely on the existance of auth.models.User, like contrib.admin. > > Personally, I think a lot of the apps in django.contrib have a lack of > flexibility. Maybe it's good to leave these apps as they are, but > start something like contrib_v2, as the improved version. > > -- > 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 > (mailto:django-developers@googlegroups.com). > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com > (mailto:django-developers+unsubscr...@googlegroups.com). > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > -- 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.
