On Sun, Aug 21, 2011 at 2:52 PM, Matt Schinckel <m...@schinckel.net> wrote: > You haven't really provided a reason why to 'do it the django way', rather > than inheriting from User.
Here is the top one: Extending the user object will make your project incompatible with 3rd party pluggable apps, as they will not be using your inherited User model, they will be using django.contrib.auth.models.User. UserProfiles, however you implement them, are cumbersome and unwieldy, but for interop reasons they remain the best way of extending the user model. Using a separate profile for each app is also wise, since it separates logically unrelated data. There is also very little reason to define settings.AUTH_PROFILE_MODULE apart from making user.get_profile() work, and if you use a one-to-one field, the difference is then user.get_profile() // user.myapp_profile . Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
