Is this an yes, a no, a maybe? It would be a pretty useful option.
On Oct 16, 12:43 am, Gary Wilson <[EMAIL PROTECTED]> wrote:
> Russell Keith-Magee wrote:
> > On 10/13/07, Joseph Kocherhans <[EMAIL PROTECTED]> wrote:
> >> I know the argument list for form_for_model is getting long, but
> >> excl
Russell Keith-Magee wrote:
> On 10/13/07, Joseph Kocherhans <[EMAIL PROTECTED]> wrote:
>> I know the argument list for form_for_model is getting long, but
>> excluding fields is just so damn useful ;)
>
> +1 from me. Personally, I'm in favour of making form_for_model as
> flexible as possible.
I
On Sun, 2007-10-14 at 20:47 +0800, Russell Keith-Magee wrote:
> On 10/13/07, Joseph Kocherhans <[EMAIL PROTECTED]> wrote:
> >
> > I'd like to add an 'exclude_fields' keyword argument to
> > form_for_model, etc. exclude_fields would be a list of field names
> > that should be excluded from the form
On 10/13/07, Joseph Kocherhans <[EMAIL PROTECTED]> wrote:
>
> I'd like to add an 'exclude_fields' keyword argument to
> form_for_model, etc. exclude_fields would be a list of field names
> that should be excluded from the form. If both 'fields' and
> 'exclude_fields' were passed in, exclude_fields
django-developers@googlegroups.com
> Subject: Proposal: form_for_model exclude_fields
>
>
> I'd like to add an 'exclude_fields' keyword argument to
> form_for_model, etc. exclude_fields would be a list of field names
> that should be excluded from the form. If both
I'd like to add an 'exclude_fields' keyword argument to
form_for_model, etc. exclude_fields would be a list of field names
that should be excluded from the form. If both 'fields' and
'exclude_fields' were passed in, exclude_fields would win for any
field that existed in both lists. Any objections
