Changing AppConfig.name to just "app" leads to ModuleNotFoundError: No
module named 'app'.
Changing the path in INSTALLED_APPS to "prefix.app.apps.AppConfig"
instead leads to the same NodeNotFoundError as before.
On Thu, 18 Mar 2021 at 15:06, Hanne Moa <hanne....@gmail.com> wrote:
>
> I have some migrations that runs/tests fine on Django 3.0 and 3.1, but
> not on 3.2b1.
>
> There's a specific app whose migrations fail with:
>
> django.db.migrations.exceptions.NodeNotFoundError: Migration
> prefix_app.000N_fooFoo dependencies reference nonexistent parent node
> ('app', '000M_bar').
>
> Which migration it is varies between runs, and note that the first app
> label looks different than the second. Is there some new way to
> auto-generate app labels that leads to this?
>
> In INSTALLED_APPS the app in question is by path: "prefix.app". In the
> AppConfig, "name" is identical to the path, "prefix.app", while
> "label" is "prefix_app". The models do not have an explicit tablename
> set and in the database they have been created with
> "app_modelnameinlowercase", not "prefix_app_modelnameinlowercase".
>
>
> HM
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/CACQ%3Drrf6gLTENCnoiUmuM7KAwBefbGD7Db4LU1ume2bbEODfWg%40mail.gmail.com.
