I started playing with subclassing the auth models today. What's nice is that when you subclass User with, say, UserProfile, all users get a .userprofile property, so the functionality of get_profile() is there for free with the bonus of multiple User subclasses if that's needed. I was thinking it might be useful if there was a setting like AUTH_USER_CLASS so that the specified subclass of User is used for request.user, create_user(), authenticate(), login(), the auth views, etc.
Maybe something like this is already in the plans, since get_profile() seems out of place or needs updating for use with inheritance, but I couldn't find anything about it. cheers, Justin --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---