https://docs.djangoproject.com/en/1.11/topics/signals/#receiver-functions
We’ll look at senders a bit later, but right now look at the **kwargs argument. All signals send keyword arguments, and may change those keyword arguments at any time. In the case of request_finished, it’s documented as sending no arguments, which means we might be tempted to write our signal handling as my_callback(sender). This would be wrong – in fact, Django will throw an error if you do so. That’s because at any point arguments could get added to the signal and your receiver must be able to handle those new arguments. On Tue, Jun 27, 2017 at 4:14 PM, yingi keme <[email protected]> wrote: > So i want to know, when using a model signals. The reciever function has > **kwargs. What is the content of **kwargs in this reciever function below: > > @reciever(post_save, sender=MyModel) > def func(sender, instance, **kwargs): > # some action. > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/django-users. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/django-users/504e60a9-9ef7-4dc6-a1a8-ab734f250455%40googlegroups.com > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CALn3ei0kP77zFO_WDPDptZPg7GWOdkyZwtN6sJ9W07d9ruZicg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
