There was an old thread about this at https://groups.google.com/group/django-developers/browse_frm/thread/6e41ee7b08d50710/9cf6375d97bed499?lnk=gst&q=update+signal#9cf6375d97bed499 which fizzled out last summer with no conclusion. (I'd reply to that thread but google groups apparently won't let me reply to something that old.)
The ticket is at https://code.djangoproject.com/ticket/13021 I want this feature for much the same reason as Dennis: while there were suggestions in the old thread about ways to avoid DRY in code that is fully under your control, there has "not yet [been] a suggestion that integrates with third party applications without modifying them". A new signal would provide a clean, easy way to do that - and would be easily understood and documented since it would fit the existing pattern of pre_save, pre_delete, etc. If this is going to be "wontfix", it'd be great to at least see that finalized on the ticket, and maybe a note in the docs that QuerySet.update() doesn't send any signals. Thanks, - PW -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
