Clear ContentType cache between tests - #1312

Thanks for this! I agree with the reasoning, but I think it does too much, and does it quietly. Pretty much every Django project I work on has some version of this in a conftest, so I understand the motivation. A couple of thoughts:

1. If this were something every test needed, I'd expect Django to handle it in its own TestCase. Since it doesn't, I'm hesitant for pytest-django to diverge from Django's behavior by default. (I know we already do something similar for the Site cache, but I'd rather not widen that pattern without a good reason.)
2. Turning this on for everyone changes behavior for existing suites. Could we make this opt-in instead, either as a fixture users can request or enable with autouse, or as an ini option?

@bluetech thoughts?

Thanks for this! I agree with the reasoning, but I think it does too much, and does it quietly. Pretty much every Django project I work on has some version of this in a conftest, so I understand the motivation. A couple of thoughts:

1. If this were something every test needed, I'd expect Django to handle it in its own TestCase. Since it doesn't, I'm hesitant for pytest-django to diverge from Django's behavior by default. (I know we already do something similar for the Site cache, but I'd rather not widen that pattern without a good reason.)
2. Turning this on for everyone changes behavior for existing suites. Could we make this opt-in instead, either as a fixture users can request or enable with autouse, or as an ini option?

@bluetech thoughts?

Thanks @kingbuzzman, I agree this shouldn't be on by default.

Happy to wait for @bluetech, or close this in favor of a short docs note if a fixture feels like too much API for a one-liner. I’ve been experimenting locally with an opt-in django_clear_contenttypes_cache fixture in case that’s the direction you’d prefer.