Conflict with an app name of 'auth' even when not using Django auth

[Matt Robenolt]

When starting a project from scratch and I remove all of the default apps out of INSTALLED_APPS, and create an app of my own called "auth", Django traverses through and registers the django.contrib.auth models automatically.

I found the source of the problem with django.core.management.validators. At the point of including any part of this module, django.contrib.auth is added into the app_store cache in django.db.models.loading. Once it has been cached in the app_store, it overrides MY 'auth' app because cache keys are stored by doing: "app.name.split('.')[-2]".

After digging through and tracing up, I found that I could simply comment out line 3 of django/core/management/validators.py and it prevents the extra models from ever being initialized unless specifically declared in settings.py

This may or may not be the best solution for the problem, but I have patched this in on a few projects of mine without any negative consequences. I can't determine if there's a better way to actually test it.

[Matt Robenolt]

Also, to add: this problem didn't exist in 1.2.

[Matt Robenolt]

Actually, I retract my patch to fix the issue. It just masks it and unveils more issues for model testing. It appears that the problem is much more deep rooted than this and may require a design decision since I'm not sure why certain decisions were made on certain aspects in the first place. Specifically why the internal app_store cache is stored based on relative package names and not absolute.

[Jacob]

Milestone 1.3 deleted

[Aymeric Augustin]

This looks suspiciously similar to #16283, which was fixed since then.

Please reopen if your problem isn't fixed in trunk.