#3951: Django's signal framework may register listeners more than once
-------------------------------------------------------------+--------------
Reporter: Ben Slavin <[EMAIL PROTECTED]> | Owner: nobody
Status: new | Milestone:
Component: Core framework | Version:
SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch:
0
Needs_docs: 0 | Needs_tests:
0
Needs_better_patch: 0 |
-------------------------------------------------------------+--------------
Comment (by anonymous):
I have just been burned by this, and as a novice django user but a fairly
experienced python programmer, I take serious issue with the "people
rapidly become used to it" attitude. In fact, the comment by mtredinnick
on 4/7 above is more infuriating every time I read it.
In my case, I had the signal registration code in a module along with the
model to which the signal was attached. That module was being loaded (in
development/"runserver" mode) twice: once apparently for validation and
once when the module was loaded by the http subsystem. Finding this bug
report at least pointed me in the right direction, and I've "fixed" the
problem by moving the registration code elsewhere.
This is clearly not a problem with a trivial fix, but I guarantee that
people will get hung up on it. The signals architecture, something which
could otherwise be a significant win, is far less useful subject to this
sort of hidden breakage.
--
Ticket URL: <http://code.djangoproject.com/ticket/3951#comment:11>
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
-~----------~----~----~----~------~----~------~--~---
