#36083: LiveServerTestCase fails in parallel test runner if
django.contrib.auth.backends has not yet been imported
-------------------------------------+-------------------------------------
     Reporter:  Adam Zapletal        |                    Owner:  (none)
         Type:  Bug                  |                   Status:  new
    Component:  Testing framework    |                  Version:  dev
     Severity:  Release blocker      |               Resolution:
     Keywords:  TransactionTestCase  |             Triage Stage:  Accepted
  setupclass available_apps          |
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls):

 No worries Adam, I didn't think you were questioning me at all. I
 appreciate you thinking it through with me! We'll hear from others soon,
 as it's still the weekend in my timezone.

 > They'd be opting into setting available_apps on their test class, so we
 can expect them to do it correctly.

 I agree with that. I guess I'm taking the opportunity to wonder about what
 is correct: if `LiveServerTestCase` is what creates the dependency on
 `contrib.auth` purely by instantiating `WSGIHandler()`, should we expect
 that to leak to the subclasses, meaning they have to either not use the
 `available_apps` attribute ''or'' discover for themselves this tricky edge
 case and guard against it for the first time in 5.2? Again, not
 necessarily a regression/release blocker given that it's a private API,
 just polling for views since we at least have the ''option'' of preventing
 an unintentional behavior change here.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/36083#comment:8>
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/010701945df7819c-6a5d9d57-82b0-4448-908d-6bbcf2cff4d7-000000%40eu-central-1.amazonses.com.

Reply via email to