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.
i'd be more than happy with a flag like that, provided it is True by default... 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... 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.. -f -- in an atomic war, all men will be cremated equal. -- 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/20150203224931.GD19562%40obiit.org. For more options, visit https://groups.google.com/d/optout.
