I think the current behaviour is correct. Django shouldn't make any assumptions about fields not in the form since it doesn't know what will happen… In that sense I disagree with the statement:
> From my point of view when I define a ModelForm I imagine that I have to only explain what the user needs to see when the form gets rendered. To get what you want use something along the lines of: https://gist.github.com/apollo13/ef72035c5f864174ad3c968dec60d88a Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/68d1762e-0541-4ab6-8586-487f440efaaa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
