#34849: Appending django.contrib.postgres to the INSTALLED_APPS via
@modify_settings crashes.
-------------------------------------+-------------------------------------
Reporter: Mariusz Felisiak | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
Replying to [comment:5 Florian Zimmermann]:
> > First of all we run the entire test suite not random subsets of test
classes.
>
> So it's expected that the tests behave differently when I only run a
subset of them?
Of course it's not, that's the issue. The way how `@modify_settings` and
initializing `django.contrib.postgres` work are non trivial. We have here
a long standing isolation issue, revealed by
fbd16438f46bc2128926958ad24331da5d1b406f.
--
Ticket URL: <https://code.djangoproject.com/ticket/34849#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018ab22d2329-384c0c8d-13d9-47bb-91f8-5fc0877bfe65-000000%40eu-central-1.amazonses.com.
