Hello,
Am 05.03.2016 um 02:57 schrieb Curtis Maloney:
> Well, Widgets and Fields are involved in determining how to extract data from
> the submitted dict... but they don't actually "parse" the http form data --
> Django does that much further down the stack in the HttpRequest object.
>
>
> As m
Hi,
On 04/03/16 07:00, 'Moritz Sichert' via Django developers
(Contributions to Django itself) wrote:
Hello,
I want to propose a refactor of the Form class to make it
easier to customize and subclass.
I've recently had thoughts in this direction, so seeing your post
intrigued me...
Howeve
Hi
On Thursday, March 3, 2016 at 9:00:47 PM UTC+1, Moritz S. wrote:
>
> For example, it's conceivable that the form data doesn't
> come from a HTTP request with x-www-form-urlencoded or
> multipart/form-data content but gets transferred as JSON. In
> this case it should be easy to replace the H
Hello,
I want to propose a refactor of the Form class to make it
easier to customize and subclass.
Motivation:
Currently the Form class (combined with Field, Widget and
BoundField) has many responsibilities and combines much
functionality into a single class. It currently does:
- data validati
