#19167: When running tests, Django accesses the database referred to in settings
-------------------------------+--------------------------------------
Reporter: EvilDMP | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.4
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by EvilDMP):
Maybe I should find a better way to do what I am trying to do, then, that
avoids this (if it is even possible, I don't know).
However, I wasn't aware that accessing the DB when modules are imported is
a bad idea in general, or that it could interfere with tests.
Is it worth making a note of this on the test documentation, or anywhere
else, if it's not already made clear that it's something one should not
do?
--
Ticket URL: <https://code.djangoproject.com/ticket/19167#comment:4>
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
