#33190: If signals will be executed when running loaddata, then provide a
warning
-----------------------------------------+------------------------
Reporter: Dan Swain | Owner: nobody
Type: New feature | Status: new
Component: Uncategorized | Version: dev
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
I just got burned when loading a large fixture file: the loading of the
file caused email confirmations for registration for an event that was
held last year to be sent again because the sending of the confirmations
happened in a post_save signal.
Without debating the merits of signals (this code should obviously not
have been put into a signal), as a feature request, I would like to see
loaddata check for the possible execution of signals. If possible
execution of signals is detected, then loaddata should stop running and
display a message that signals might be triggered. The user could then
either temporarily comment out any signals in the code and re-run loaddata
(likely the most desired behavior), or they should be required to specify
an override flag if re-executing loaddata without commenting out signals
(something like loaddata fixture_name --execute-signals).
--
Ticket URL: <https://code.djangoproject.com/ticket/33190>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/054.c97bb7d9dd680add5d57c14bb9df780f%40djangoproject.com.
