I just wanted to write a preliminary post about this before gathering a little more data. When extending a non-abstract model (Python inheritance) it seems to me that a pre_delete signal registered to the parent model is fired when an inherited model is deleted—which would be expected. A pre_save signal registered to the parent model, however, does not seem to be firing when saving the inherited model. I am not sure if this is desired behavior, but it is slightly confusing.
— pre_delete registered on parent model: fired — pre_save registered on parent model: not fired I came upon this case when extending the djcelery PeriodicTask object. When creating an instance of an inheriting model, the pre_save signal was not sent, but the pre_delete signal did seem to be sent. Any thoughts? I can get around this by manually registering the inheriting model. aryeh -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/abf443b2-0ded-41e0-b9f0-b2ad788de5c0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
