#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
-------------------------------------+-------------------------------------
Changes (by bmispelon):
* status: new => closed
* resolution: => worksforme
Comment:
Hi,
I've tried to reproduce your issue but couldn't manage to get the results
you're describing.
I used an empty `Foo` model (no fields except for the auto-generated `id`
one) and the following code:
{{{#!python
from django.db.models.signals import pre_save
from django.dispatch import receiver
from bug22657.models import Foo
@receiver(pre_save)
def callback(sender, **kwargs):
print('Hello!')
Foo.objects.create() # Prints "Hello"
pre_save.disconnect(callback)
Foo.objects.create() # Prints nothing
}}}
I've tried both `master` and the 1.6 branch and I get the same result in
both cases.
Could you show us a piece of code that demonstrates the issue (and reopen
this ticket when you do so)?
Thanks
--
Ticket URL: <https://code.djangoproject.com/ticket/22657#comment:2>
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.4a208274155a09e9056693ff8828f0d0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
