Re: ModelForm.Meta.overrides

(ticket #2 that is) On Friday, June 7, 2013 1:36:30 PM UTC-4, Tim Graham wrote: > > I'd like to revive the discussion here. I think making simple > customizations to the default ModelForm fields is a common need that we > should try to find some

Re: ModelForm.Meta.overrides

I'd like to revive the discussion here. I think making simple customizations to the default ModelForm fields is a common need that we should try to find some way to address. Another shot at this is "#2000 -- Allow overriding `label`, `help_text` and

Re: ModelForm.Meta.overrides

Simon, > A couple of months ago Jannis closed #/17924 [1] as wontfix, stating "I'm > violently -1 on the whole topic "meta programming form fields after they've > been instantiated", it's a mess. Yes it would be more DRY, but also much > harder to know how the hell the form fields are composed

Re: ModelForm.Meta.overrides

Overall, I like this patch. I think it's a little unbalanced that we provide `Meta.widgets` but no clearly documented way to override other properties on fields without replacing entire fields. I think the doc changes are pretty helpful to users who are looking for a way to do this, and it is a

ModelForm.Meta.overrides

A couple of months ago Jannis closed #/17924 [1] as wontfix, stating "I'm violently -1 on the whole topic "meta programming form fields after they've been instantiated", it's a mess. Yes it would be more DRY, but also much harder to know how the hell the form fields are composed as. Just override t