I agree that there is no one model that fits everyone's needs. Instead, I think it would be nice if the user model to use could be configurable. The admin application currently expects auth User objects, when it should instead expect an object that conforms to an interface, similar to the changes that multi auth brought.
One thing that would make this easier, for example, would be to break the permission methods out of auth User into an ObjectWithPermissions class. Now, if I want one of my models to have permissions (like my own user model), then I could simply inherit ObjectWithPermissions. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
