#37064: SimpleTestCase._remove_databases_failures() crashes on un-wrapped
connection methods
-------------------------------------+-------------------------------------
Reporter: Rio Weber | Owner: (none)
Type: Bug | Status: new
Component: Testing framework | Version: 6.0
Severity: Normal | Resolution:
Keywords: testcase, | Triage Stage:
databases, multi-db, regression | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Rio Weber):
Replying to [comment:1 Simon Charette]:
Humm, good call. I thought it was Django by default because I found the
#36942 ticket.
I'll investigate and check back
> Thanks for spending time reproducing the issue with Claude Rio.
>
> Given this can only be reproduced with `pytest-django` though I do
wonder if the issue doesn't lie over there instead. What does `pytest-
django` do that causes SQLite to recycle the connection between
`setUpClass` and `tearDownClass` that Django doesn't do?
>
> The fact `pytest-django` swaps `connections` entries makes me worried
that they have flawed logic on their side that defeats the purpose of the
database query prevention mechanisms that Django puts in place.
>
> Nothing seems to indicate that Django is at fault here.
--
Ticket URL: <https://code.djangoproject.com/ticket/37064#comment:2>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019dc1845c57-c0a135f7-f7ef-491b-b4fb-db1d606273df-000000%40eu-central-1.amazonses.com.
