#27312: Current solution to prevent signals from executing on fixtures is non
ideal
----------------------------------+--------------------------------------
Reporter: Álex Córcoles | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.10
Severity: Normal | Resolution:
Keywords: fixtures signals | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Changes (by Simon Charette):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Is there a reason you can't use data migrations (`RunPython` operations)
to load your fixtures?
Models provided in data migrations through the `apps` kwarg are not
connected to any signals so you should be able to achieve what you're
after this way. Please give #24778 a try if that works for you.
Not running signals during fixture loading is not only controversial, it's
breaking backward compatibility.
--
Ticket URL: <https://code.djangoproject.com/ticket/27312#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 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/065.07466e16a48241b1819993fcf544665d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
