While trying out Django 1.8 with one of my sites that uses a custom User model (and doesn't have django.contrib.auth in INSTALLED_APPS), I noticed a few unexpected deprecation warnings:
/Users/dcwatson/Documents/Environments/reader/lib/python3.4/site-packages/django/contrib/auth/models.py:41: RemovedInDjango19Warning: Model class django.contrib.auth.models.Permission doesn't declare an explicit app_label and either isn't in an application in INSTALLED_APPS or else was imported before its application was loaded. This will no longer be supported in Django 1.9. class Permission(models.Model): Same thing for User and Group. Is it required to have django.contrib.auth installed to use custom User models now? Seems like it would be easy enough to move AbstractBaseUser (and probably UserManager/BaseUserManager) to a separate modules and import them from django.contrib.auth.models, so sites could use them without triggering these errors. If this sounds reasonable, I can open a ticket/PR. Dan -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" 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. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/02f98a6f-9fbf-4c57-8285-80f3c2c3e2ef%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
