On Wed, Nov 4, 2015 at 11:58 PM, victor menezes <[email protected]> wrote:
> I agree that it is time for django to change it (at least making the > changes easier) > I’m intrigued - exactly how much easier do you want us to make it? At this point, it is *literally* installing a third party app, adding that app to INSTALLED_APPS , and adding an AUTH_USER_MODEL setting to your configuration file. Changing the default isn’t a viable option, because changing the default user would break *every* Django project that assumes the current default User model is the one in existence - which is to say, every Django project generated to date that hasn’t deployed a custom User model. We’ve also had an open ticket #20824: https://code.djangoproject.com/ticket/20824 This would add an EmailUser as part of Django’s core. However, there are some techncial issues associated with this: https://groups.google.com/d/msg/django-developers/7feYlp9HqKs/Z_vv8O43vEUJ We haven’t worked out how to resolve these issues; if there are any suggestions, the idea has broad support from the core team. Yours Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAJxq84_G%2BSqrzHuu%2B0xU8wPw%2BrWj9jJGLmvduHf4gEw%2BnggtTg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
