Absence of **kwargs would cause problems if for example save method is called with "using" keyword argument. You could either list all the available keyword arguments or use **kwargs.
By the way, is there any other kwarg for save? 2011/8/16 Mike Dewhirst <mi...@dewhirst.com.au> > When using save() in a model, what is the difference between ... > > save(self, force_insert=False, force_update=False) or > save(self, force_insert=False, force_update=False, **kwargs) > # whatever > super(Xyz, self).save(force_insert, force_update) or > super(Xyz, self).save(force_insert, force_update, **kwargs) > > and > > save(self, *arg, **kwargs) > # whatever > super(Xyz, self).save(*args, **kwargs) > > I see the former in a fair bit of django example code around the place and > the latter in the docs here > > > https://docs.djangoproject.com/en/dev/topics/db/models/#overriding-predefined-model-methods > > Thanks for any insights > > Mike > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
