#34193: TestCase _fixture_teardown breaks database MIRROR usage ---------------------------------------------+------------------------ Reporter: Jean-Daniel | Owner: nobody Type: Bug | Status: new Component: Testing framework | Version: 4.1 Severity: Normal | Keywords: Triage Stage: Unreviewed | Has patch: 0 Needs documentation: 0 | Needs tests: 0 Patch needs improvement: 0 | Easy pickings: 0 UI/UX: 0 | ---------------------------------------------+------------------------ The TestCase class _fixture_teardown() implementation try to iterate over all databases while it should ignore MIRROR databases.
Trying to include MIRROR database in the iteration loop make the teardown be execute twice on the database and raise an exception. {{{ for db_name in reversed(self._databases_names()): }}} Should be {{{ for db_name in reversed(self._databases_names(include_mirrors=False)): }}} -- Ticket URL: <https://code.djangoproject.com/ticket/34193> 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 django-updates+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/01070184c946dda8-3d947f30-09dc-496e-bdd5-01db0852af3c-000000%40eu-central-1.amazonses.com.