#24816: Clarify docs about preventing duplicate signals
-------------------------------------+-------------------------------------
Reporter: Timothy Makobu | Owner: Jason
Type: | Held
Cleanup/optimization | Status: closed
Component: Documentation | Version: 3.1
Severity: Normal | Resolution: fixed
Keywords: signals | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"703256fc681338bc227768a15c1f56851d05adae" 703256f]:
{{{
#!CommitTicketReference repository=""
revision="703256fc681338bc227768a15c1f56851d05adae"
[3.1.x] Fixed #24816 -- Clarified docs about preventing duplicate signals.
Backport of 639142e24d41c5e5a508cb1280f32fd7ff159cca from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24816#comment:9>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.bb3e0fae0f97ec96df994179d041b8a5%40djangoproject.com.
