#22254: Testing documentation doesn't make it clear that django.setup() needs 
to be
called with setup_test_environment
-------------------------------------+-------------------------------------
     Reporter:  peter.landry@…       |                    Owner:  Tim
         Type:                       |  Graham <timograham@…>
  Cleanup/optimization               |                   Status:  closed
    Component:  Documentation        |                  Version:
     Severity:  Normal               |  1.7-alpha-2
     Keywords:  app-loading          |               Resolution:  fixed
    Has patch:  0                    |             Triage Stage:
  Needs tests:  0                    |  Unreviewed
Easy pickings:  0                    |      Needs documentation:  0
                                     |  Patch needs improvement:  0
                                     |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):

 * owner:   => Tim Graham <timograham@…>
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"26b03f25265227498a2559af807918fe2a1d246f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="26b03f25265227498a2559af807918fe2a1d246f"
 Fixed #22254 -- Noted the requirement of calling django.setup() when
 running

 Thanks Peter Landry for the report.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/22254#comment:9>
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 post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/080.8e38106b84b9a669095b252e44708c9e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to