This is a continuation of my post on stackoverflow<http://stackoverflow.com/questions/18769729/django-removing-username-from-user-model> .
With the introduction of Django 1.5, it was possible to create a custom User model which is flexible enough to have any user profile the developer wants created. However, looking at a very common problem which is using the email as the primary user identifier instead of username, the solution requires copying most of Django's internal definition of AbstractUser and that is only to remove the username field. A better solution in my opinion is make AbstractUser even more abstract by removing username field, and allowing the developer to explicitly specify the field to be used as the user identifier. This will require a tiny extra work for those that use the current default behavior, but it will also greatly reduce the work needed for the very common problem of using email as the user identifier. Please share your thoughts and opinions on this. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
