Documentation: Explicit is better than implicit.
|Reported by:||arbitraryuser||Owned by:||nobody|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
The short version:
I think it might make sense to modify the documentation at http://docs.djangoproject.com/en/dev/topics/forms/modelforms/#the-save-method to say
>>> f = ArticleForm(data=request.POST) rather than just
>>> f = ArticleForm(request.POST) as users will run into 'non-keyword arg after keyword arg' issues when using more advanced incantations of ModelForm.
The long version:
I ran into a problem with http://docs.djangoproject.com/en/dev/topics/forms/modelforms/#the-save-method because I was passing my form def an additional varible with which to limit the options of drop down box. This works fine until you are also doing a ModelForm based update and need to pass data, your instance *and* an object that you want to filter with. I had to in the source to see what the arg's name actually was.
PS. Loving Django so f-ing much right now... :)