#35952: Internal test runner requirement for TransactionTestCase to set
available_apps raises TypeError
-------------------------------------+-------------------------------------
               Reporter:  Jacob      |          Owner:  Jake Howard
  Walls                              |
                   Type:             |         Status:  assigned
  Cleanup/optimization               |
              Component:  Testing    |        Version:  dev
  framework                          |
               Severity:  Normal     |       Keywords:
           Triage Stage:             |      Has patch:  1
  Unreviewed                         |
    Needs documentation:  0          |    Needs tests:  0
Patch needs improvement:  0          |  Easy pickings:  0
                  UI/UX:  0          |
-------------------------------------+-------------------------------------
 Reported by Jake Howard in [https://github.com/django/django/pull/18628
 PR]:

 The internal test runner (`runtests.py`) requires that `available_apps` be
 set as a class attribute on `TransactionTestCase` subclasses, but
 accomplishes this with a `property`. After
 8eca3e9bce519c21340312ee7846c92b27abea79, it needs to be a
 `classproperty`.

 To reproduce, alter one of Django's `TransactionTestCase` subclasses to
 remove the `available_apps` attribute:
 {{{
 ------------------
 Traceback (most recent call last):
   File "/Users/.../django/django/apps/registry.py", line 318, in
 set_available_apps
     available = set(available)
 TypeError: 'property' object is not iterable
 }}}

 Regression in 8eca3e9bce519c21340312ee7846c92b27abea79, but not marking as
 a release blocker or needs tests since this is an internal tool only and
 not tested.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/35952>
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/01070193782ea626-1a16c807-c001-4b7b-9dde-009970d97d37-000000%40eu-central-1.amazonses.com.

Reply via email to