#22657: Can't disconnect signal if connected using @receiver tag
-------------------------------------+-------------------------------------
Reporter: michalsicker@… | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.6
(models, ORM) | Resolution:
Severity: Normal | worksforme
Keywords: @receiver signal | Triage Stage:
disconnect | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by James Addison):
Note this comment made in #28169:
https://code.djangoproject.com/ticket/28169#comment:1 It shows that there
are cases where `.disconnect()` isn't as easy as it 'should' be, but it
can be made to work.
--
Ticket URL: <https://code.djangoproject.com/ticket/22657#comment:5>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/080.5fb4e60ee53544067de6e140d48b32d4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
