#33505: Inconsistent Behavior with Abstract Models and Signals
-------------------------------------+-------------------------------------
Reporter: Ken Weaver | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Ken Weaver):
Yes I understand, but as the code above demonstrates, when adding a
receiver for a `m2m_changed` signal and `Abstract.m2m_field.through` field
as the sender, the code operates the same as if the sender was `None`.
This, not the fact that `pre_save`, `post_save` etc. signals are not
automatically sent for abstract models, is the peculiar behavior that led
to this ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/33505#comment:4>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.a36a7811a80f69f30e3c214175cc6a6e%40djangoproject.com.
