Its implementation can look something like this:
{{{#!python
def _value_from_datadict(self, field, html_name):
return field.widget.value_from_datadict(self.data, self.files,
html_name)
}}}
One reason this is nicer is that callers don't have to know about the
form's `self.data` and `self.files` dicts. They can just access a method
on the form, which encapsulates the data dictionaries.
--
Ticket URL: <https://code.djangoproject.com/ticket/32917>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/32917#comment:1>
* has_patch: 0 => 1
Comment:
PR: https://github.com/django/django/pull/14629
--
Ticket URL: <https://code.djangoproject.com/ticket/32917#comment:2>
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"4be58fcc369a024bd7ac72bb09af7d230499cccb" 4be58fc]:
{{{
#!CommitTicketReference repository=""
revision="4be58fcc369a024bd7ac72bb09af7d230499cccb"
Fixed #32917 -- Added BaseForm._widget_data_value()/_field_data_value().
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32917#comment:3>