> Deprecate pre_init and post_init signals. I wonder if these are > actually used in third-party code. These signals are not the easiest > to use, as they get the field values in *args, or in **kwargs, or part > in *args, part in **kwargs. Django core uses them in generic foreign > keys: >
To leap in here - we use post_init in our application, so there's at least *one* consumer out there! We use them to populate attributes on a model which depend on other system state, including data in that model itself. In our case, we actually only care about the instance passed in kwargs. There may be another way of doing what we're doing without post_init, but I'd need to look into it. Cheers Dan -- Dan Fairs | [email protected] | www.fezconsulting.com -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
