Jeroen Brouwer

Awesome, thanks for the response!

I fixed it in https://github.com/bernardopires/django-tenant-schemas/pull/567 unfortunately there hasn't been any feedback/progress on this project, so I just use the PR version in my project.

> As @Solanar said, this is related to the start method. A very simple workaround is to include this in startup (windows or OS X, but should be a no-op...

The `master` branch of this repo has diverged a bit over the years, probably best to extract the useful bits into a separate branch and do a PR from there?

Thanks for the suggestion, it doesn't solve it unfortunately.

Somehow it always worked without marking the individual tests with `pytest.mark.django_db` until now.... Fixed for me, so I'm closing this issue.

Reopening because the problem still occurs when running this in my CI pipeline. Downgrading to `4.6` fixes it.

> Argh sorry I didn't mean hook/hookwrapper, I meant fixture/yield fixture. You should write it like this: > > ```python > @pytest.fixture(scope="session", autouse=True) > def django_db_setup(django_db_setup, django_db_blocker): > with django_db_blocker.unblock():...

> Yes, it's probably fine, just something to try. The important thing is to make sure to request `django_db_setup` from your own `django_db_setup`. The thing is that it always worked,...

Same issue here, saving/reformatting files changes the import order. Currently I'm just running a tiny script that does a `ruff check --fix` and `ruff format` when I'm done changing files....