#10868: _destroy_test_db exposes the production database to possibly destructive
actions from the unit tests
-------------------------------------+-------------------------------------
Reporter: ovidiu | Owner: nobody
Type: Bug | Status: new
Component: Testing framework | Version:
Severity: Release blocker | Resolution:
Keywords: django.test | Triage Stage: Design
Has patch: 1 | decision needed
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by julien):
Users who intentionally let threads live and create new connections after
the test database is supposedly destroyed are really asking for trouble
and are likely already affecting their production database :)
So in my opinion this change would be backwards compatible, at least in
the general case. However, if some users come up with genuine use cases
then we could consider wrapping this new behaviour into a `TestCase`
method so that one can modify it to their heart's content.
--
Ticket URL: <https://code.djangoproject.com/ticket/10868#comment:17>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
