Also, even if we decide to use django-primate's monkey patch to mount a user model on django.contrib.auth.models.User I think we should still consider breaking AbstractUser into orthogonal mixins. As it stands, AbstractUser is a monolithic model with an ad-hoc method for overriding fields. As a result, it is difficult to reason about what effect modifying a particular field will have.
Is it valid to rip out all of the personal info and authentication mechanisms and just use twitter handles with contrib.admin? If contrib.admin only depends on a permissions mixin then sure. Otherwise each field you remove is an unknown risk. Alex Ogier -- 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.
