Django m2m_changed signal is never called

Question

I can't understand why my m2m_changed signal is not triggered.

Here is the code:

models.py

class Badge(TimeStampable, Expirable, Deactivable,
            SafeDeleteModel):
    _safedelete_policy = HARD_DELETE

    owner = models.ForeignKey(settings.AUTH_USER_MODEL,
                              blank=True, null=True,
                              on_delete=models.PROTECT)
    restaurants = models.ManyToManyField(Restaurant)
    identifier = models.CharField(max_length=2048)

    objects = SafeDeleteManager.from_queryset(BadgeQuerySet)()

signals.py

from django.db.models.signals import m2m_changed
from django.dispatch import receiver

from .models import Badge

@receiver(m2m_changed, sender=Badge.restaurants.through)
def my_callback(sender, **kwargs):
    print("M2M has been changed!")

apps.py (this post advised to change this file)

from django.apps import AppConfig

class BadgesConfig(AppConfig):
    name = 'badges'

    def ready(self):
        import badges.signals

When going to a shell:

m2m_changed.receivers returns an empty list (it does not work, and the signal can never be received)

I found similar post but did not found the answer in it.

Why m2m_changed signal does not work?

EDIT

When opening a shell and importing badges.signals, it works. It means the problem is in apps.py:

In [1]: from django.db.models.signals import m2m_changed

In [2]: m2m_changed.receivers
Out[2]: []

In [3]: import badges.signals

In [4]: m2m_changed.receivers
Out[4]:
[((4551224720, 4520068792),
  <weakref at 0x10f4da5e8; to 'function' at 0x10f462d90 (check_uniqueness)>)]

Please do `from django.db.models.signals import m2m_changed` and post (in your question) what this gives you: `m2m_changed.receivers` (if it isn't an empty list, in which case the signal was not connected). — CoffeeBasedLifeform, May 31 '18 at 16:16
Try adding `m2m_changed.connect(my_callback)` to the end of signals.py and check `m2m_changed.receivers` again. (Might have to remove the receiver decorator from your callback). — CoffeeBasedLifeform, May 31 '18 at 16:50
Try importing `badges.signals` in your app's `__init__.py` as mentioned here: [click](https://stackoverflow.com/a/27038181/9313033). (Either the init.py in the folder with settings.py or your app's main folder should work) — CoffeeBasedLifeform, May 31 '18 at 18:05
Seems it's not related to how signals are import because it works for another type of signal (see my updated question). — David Dahan, May 31 '18 at 19:08
No, I mean what code are you using to make the m2m trigger, i.e. like `badge_obj.restaurants.add(rest_obj)` or similar? — Benjamin Hicks, Jun 02 '18 at 14:21
Just giving my 2p's worth: have you tried `@receiver(m2m_changed, sender=Badge.restaurants.through, weak=False)`? — Jacques Gaudin, Jun 02 '18 at 18:43
@JacquesGaudin I tried with `weak=False` but nothing changed. @SardorbekImomaliev `__init__.py` is empty, but that's expected because I use `apps.py` to register the signal, as advised in documentation. (I already tried with the __init__ method and did not work) — David Dahan, Jun 04 '18 at 10:04
When opening a shell and importing badges.signals, it works. It means the problem is in apps.py!! (question edited). — David Dahan, Jun 04 '18 at 10:27

score 9 · Accepted Answer · answered Jun 04 '18 at 10:54

I found my mistake in this section of Django the documentation. From the beggining, my apps configurations were never called!

Actually, to register an app correctly, I have two methods:

method 1

INSTALLED_APPS = ['badges', ...]

and declaring in __init__.py: default_app_config = 'badges.apps.BadgesConfig'

method 2

INSTALLED_APPS = ['badges.apps.BadgesConfig']

my mistake

I was using the INSTALLED_APPS = ['badges', ...] without declaring anything in __init__.py

I think maybe Django could display a warning when it notices that apps.py is in a folder app but never used.

Django m2m_changed signal is never called

1 Answers1