#17928: Tests with import time dependency on DB fail
-----------------------------------+--------------------------------------
     Reporter:  boxm               |                    Owner:  nobody
         Type:  Uncategorized      |                   Status:  closed
    Component:  Testing framework  |                  Version:  SVN
     Severity:  Normal             |               Resolution:  needsinfo
     Keywords:                     |             Triage Stage:  Unreviewed
    Has patch:  0                  |      Needs documentation:  0
  Needs tests:  0                  |  Patch needs improvement:  0
Easy pickings:  1                  |                    UI/UX:  0
-----------------------------------+--------------------------------------
Changes (by carljm):

 * status:  new => closed
 * needs_docs:   => 0
 * resolution:   => needsinfo
 * needs_tests:   => 0
 * needs_better_patch:   => 0


Comment:

 Do you have a legitimate use case for an import-time database query? In
 non-test code, those are almost always bugs, as they result in data that
 never gets updated until a process restart; so it's a good thing if they
 fail under test.

 Marking needsinfo, as without more detail I don't think this is a valid
 use case that should be supported. If you feel you have a strong use case
 that can't easily be handled any other way, reopen. My inclination is to
 close this wontfix.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/17928#comment:1>
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.

Reply via email to