> This is pretty much exactly what django-primate does, except it includes a > special metaclass to allow > overriding of default fields.
Yeah, that is the basic idea. I think that permissions and associated code should be moved from UserBase to live directly on auth.User or in a mixin of their own (they are mostly orthogonal to authentication, yes?) so that writing one's own base user is easier, but the monkey-patch looks like it is implemented in a nice way. So long as writing your own base is easy enough, the extra special-case metaclass and field overriding isn't strictly necessary, and can wait until explicitly overriding fields has proper support in core (something I think will be generally useful). -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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
