with nested applications different applications ordering cause wrong app_label for some models

[Raffaele Salmaso]

I've a project with this layout

project
project.myapp
... # other apps

project and project.myapp have both models.py
project.myapp.models has MyModel defined

If I have
INSTALLED_APPS = (

'project.myapp',
'project',

)
django recognize project.myapp.models.MyModel correctly as myapp.MyModel.

otherwise if I have
INSTALLED_APPS = (

'project',
'project.myapp',

)
django recognize project.myapp.models.MyModel incorrectly as project.MyModel.

[Aymeric Augustin]

I assume you meant "incorrectly" in the last line. If so, that's probably the same issue as #23348. Make sure your project app doesn't import models from project.myapp.

Your title says "migrations" but I'm not sure how this is related to migrations.

[Raffaele Salmaso]

Yes, I mean 'incorrectly'.

I'm porting a large project already in production to 1.7 so probably there is some import left, I'll check if it's the same issue of https://code.djangoproject.com/ticket/23348.

I say "migrations" because I find the problem with makemigrations, and only one app is misbehaving, the others are fine (all nested).