#8399: loaddata management command should provide option to disable signals
--------------------------------------------+-------------------------------
Reporter: [EMAIL PROTECTED] | Owner: nobody
Status: new | Milestone: post-1.0
Component: django-admin.py | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
--------------------------------------------+-------------------------------
Changes (by mtredinnick):
* needs_better_patch: => 0
* needs_docs: => 0
* stage: Unreviewed => Accepted
* needs_tests: => 0
* milestone: => post-1.0
Comment:
This solution is a bit too heavy-handed. Disabling all signal handling
just because some of your signal methods don't need to be run in that
situation is wrong. There will be plenty of cases where loading data
should trigger other behaviour that must be run whether the data is coming
in through loaddata or otherwise (e.g. creating a related object, such as
a user profile).
Your problem has some legitimacy, but your proposed solution is throwing
out the baby with the bathwater.
--
Ticket URL: <http://code.djangoproject.com/ticket/8399#comment:1>
Django Code <http://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
-~----------~----~----~----~------~----~------~--~---
