Why does django not do for the User model the same as it does for the userprofile model?
"Why doesn't django just have the model to use for User configured in the settings file?"
I have a  site that doesn't need users or a login or authentication. 
I don't want the model for User.
In order to support everyone with applications like mine, User is optional.
Why doesn't django just have the model to use for User configured in the settings file?
The requirements on the model specified would be that it contain a certain set of fields.
Is there a reason why it couldn't be done this way?