On Thu, Apr 12, 2012 at 12:19 PM, Carl Meyer <c...@oddbird.net> wrote: > Also, it isn't really true that the model signals are strictly tied to > database activity; they are tied to events on Python model objects. One > of the three signals under discussion is the pre/post_init signal, which > fires anytime a model instance is instantiated, even if no database > query or database change occurred.
i think this is the semantic issue that should be explicit: if those signals are for _every_ model, then should fire for abstract parents and abstract children (proxy models). maybe a 'fire_signals' meta option that defaults to False on abstract parents and True on proxy (and normal) models? -- Javier -- 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.
