Pascal Chambon

I have similar issues when trying to call django-compat-patcher setup before django.setup(). Is it necessary that django.setup() gets called so early in pytest loading system ? Isn't it psosible to...

OK I see the point of having django already setup at conftest stage then. I don't think we need to make anything backwards incompatible, this new setting ("--django-setup" ?) would...

Yes I did use this instruction for changing app before django sets up, but since nothing is configured (no python paths, no conftests...), it forces me to keep a pytest...

I'm just thinking : why not add an option, in pytest-django, similar to that of pytest-pythonpath ? Since it sets up very early, maybe pytest-django shouldbe able to configure python...

As of now I don't know if this way of solving the problem would not be more generic: https://github.com/pytest-dev/pytest-django/issues/764

The plugin can be quite short, but the big issue for me was that all this happens long before python paths are auto-detected, so I've opened a PR in the...

Well my experiments so far with early pythonpaths have failed, and I still encounter that issue of early patching of django, in my new projects. So I guess the best...

Thanks for the hint, I hadn't thought about this. In your opinion, would it be feasible (and robust) to have a flag to commit/keep the DB test data "when it's...

Just tried today with the recent 4.2.X mediaelement and playlist plugin, playlist doesn't get updated at all when current music changes.

How about "blacking" the whole repo with Black formatter ? This + optimzie-imports would solve most problems.