#24816: Preventing duplicate signals
-------------------------------------+-------------------------------------
Reporter: timkofu | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Core (Other) | Version: 1.8
Severity: Normal | Resolution: invalid
Keywords: 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 freakboy3742):
* status: new => closed
* needs_docs: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_better_patch: => 0
Comment:
The ticket tracker is for tracking known problems, not asking questions.
If you want to ask a question about usage, please use the Django-users
mailing list.
However; to answer your question: Yes, it is still a problem, and no,
there isn't much we can do about it (other than what is already listed in
in the docs). The problem is that due to Python's import process, it's
possible for the same module to be imported twice, resulting in a handler
being registered twice.
--
Ticket URL: <https://code.djangoproject.com/ticket/24816#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.cdba0fab6d762bb5d52f0306added3d8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
