#16857: new flush db signal
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
michaelritsema@… | Status: closed
Type: New | Component: Core (Management
feature | commands)
Milestone: | Severity: Normal
Version: 1.3 | Keywords:
Resolution: invalid | Has patch: 0
Triage Stage: | Needs tests: 0
Unreviewed | Easy pickings: 0
Needs documentation: 0 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by ptone):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
are you testing the args in the signal - it is sent once per app.
Since flush is supposed to mimic syncdb fully - you should not be able to
distinguish between them. The emit_post_sync_signal is only called once
inside flush - so at this point, in the absence of a clearer description,
I'll assume that you are hooking up your test loader to just the syncdb
signal, and it is firing for each app (if I'm wrong, reopen with a clearer
description of what is happening).
Also note that there is a hook for loading test specific fixtures:
https://docs.djangoproject.com/en/dev/topics/testing/#fixture-loading
--
Ticket URL: <https://code.djangoproject.com/ticket/16857#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.
