On Wed, Feb 4, 2015 at 6:49 AM, frantisek holop <[email protected]> wrote:

> Tom Christie, 03 Feb 2015 12:53:
> > Trimming at `request.POST` or at the `Form` layer absolutely isn't
> > sensible, and a `normalize` argument is probably just overcomplicating
> > things, but I got the impression from that ticket that nobody would have
> > any great issue with someone issuing a patch with a `trim_whitespace`
> flag
> > on CharFields and TextFields.
>

Jacob specifically said a good patch for this feature would be considered
when he wontfixed #6362.


> i'd be more than happy with a flag like that, provided
> it is True by default...
>

I can tell you that this *won't* happen - firstly because it will be
backwards incompatible for every Django installation out there, but also
because throwing away data that the user actually entered should be an
opt-in, not opt-out behavior.


> i don't feel strongly about any of the solutions as
> long as i don't have to change all my models to add a
> flag i always need...
>

You wouldn't be changing it on a model - it would be on the form.

i think wontfix-ing the ticket sent the wrong
> signal, and people stopped trying to seek a consensus
> on something that is perceived as a dead-end..
>

Read the comment where #6362 was closed WONTFIX, and you'll see Jacob left
the door open for a "strip"-style approach, and specifically asked of for a
patch implementing that behavior. WONTFIX is a single flag - sometimes you
need to read the context as well.

Yours,
Russ Magee %-)

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAJxq849DC-rOY_4qUnMO9DEoNCCZv_me6szFdx4PeJZf3uLaDA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to