#19668: Form enhancement: `Form.set_data` to set data and files
-------------------------------------+-------------------------------------
Reporter: bruth | Owner: nobody
Type: New feature | Status: new
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Design
Has patch: 1 | decision needed
Needs tests: 1 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 1
| UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by anonymous):
* needs_better_patch: 0 => 1
* needs_tests: 0 => 1
* stage: Unreviewed => Design decision needed
Comment:
I'm -0 on this change, but i'm not a core dev.
The argument against this would be that much of a form's functionality
changes based on data, fields, valid/invalid, cleaned data, errors etc..
Changing the data at the wrong time could cause a lot of problems.
Changing set_data to raise an error if the form is already bound may be
enough to address some of those concerns. I'd suggest raising the issue on
django-developers to get some opinions from core devs.
--
Ticket URL: <https://code.djangoproject.com/ticket/19668#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
