Re: Django's build: Try Earthly?

Hi Tom, I believe that a lot of what django-docker-box achieves is what Earthly was created for too. Now that you already have django-docker-box, it’s possible that you might not need Earthly. Or at least not for the purpose of reproducing CI integration testing locally, specifically. In any case

Re: Django's build: Try Earthly?

Hey! I've recently been trying to improve our local/CI experience so this is quite a nice and timely message! I really like the look of Earthly and it has some uses at $WORK that I'm excited about,

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 adj

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 co

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 runs

Django 3.2 release candidate 1 released.

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2021/mar/18/django-32-rc1/ -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions

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 mi