Re: Bug in migrations when testing on Django 3.2b1

*phew* old cruft indeed. I wasn't using the AppConfigs I *thought* I was using so no wonder things were flaky. It might for paranoia's sake be worth mentioning in the upgrade notes for 3.2 that if you get NodeNotFoundError when running migrations/database tests on 3.2 to double check the app

Re: Bug in migrations when testing on Django 3.2b1

Reverting didn't see to do anything but I'll spread around some breakpoints in 3.1 and 3.2 and compare what happens. I have another project, on 3.0, that I'm testing with 3.2 with the exact same naming scheme (except every app has a a label in their AppConfig, in the one that fails, not all of

Re: Bug in migrations when testing on Django 3.2b1

Looking at the history for the migrations code , the was https://github.com/django/django/commit/110001d0bbbabe2a5b57b14a59bd0e4b71bf2712#diff-e7df880bdc17c719e0332fa0cfbd4eff49bd481f638e34335a6311cfcd0ebc26 recently which

Re: Bug in migrations when testing on Django 3.2b1

Hi. So, first off, thanks for testing! Initial thoughts: * We might need a bit more to be able to reproduce — are you able to narrow down the problem? * "Which migration it is varies between runs" — that sounds fun  * "Changing AppConfig.name..." — The AppConfig loading was reworked, it

Re: Bug in migrations when testing on Django 3.2b1

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 wrote: > > I have some migrations that

Bug in migrations when testing on Django 3.2b1

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