On Sat, Aug 8, 2009 at 10:17 AM, David Haas<david.h.h...@gmail.com> wrote: > > Fair enough. I've got some style questions about the best way to do > what I want to do, but they're probably not so relevant here. > Something that might be relevant is this . . . is it worth submitting > a documentation patch for this issue? I was thinking something on > this page: > > http://docs.djangoproject.com/en/dev/topics/forms/modelforms/#using-a-subset-of-fields-on-the-form > > ... in the note box along the lines of "If you specify fields or > exclude when creating a form with ModelForm, then the fields that are > not in the resulting form will not be <new stuff>initialized by an > model instance or </newstuff> set by the form's save() method.
Absolutely. We aren't striving for ambiguity, so any suggestions on how we can clarify the docs in this regard are most welcome. Please open a ticket for the general suggestion (perhaps with a summary of the problem so we know what it is we're trying to explain); if you have some draft text, drop it in a patch or a comment. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
