You could already extend the user model with a OneToOne relation plus setting in settings.py that was supported in the official Django distribution. But the way that was handled was a bit hacky so I'm glad they changed it too.
But you still were forced to use obligatory auth.User fields like username/email, etc., while there are quite a few use cases when you curse it and the only choices were either making some really weird workarounds or dropping User altogether. Russel's solution is meant to solve this problem.
Comments
You could already extend the user model with a OneToOne relation plus setting in settings.py that was supported in the official Django distribution. But the way that was handled was a bit hacky so I'm glad they changed it too.
But you still were forced to use obligatory auth.User fields like username/email, etc., while there are quite a few use cases when you curse it and the only choices were either making some really weird workarounds or dropping User altogether. Russel's solution is meant to solve this problem.
Yea and incur an extra DB lookup every time. This is very welcome.
not to mention tastypie headaches when trying to update nested resources (user->userprofile->something else)