On 5 July 2011 02:20, Jacob Kaplan-Moss <ja...@jacobian.org> wrote: > Doesn't do anything to change my point, though: a framework can't go > about stripping user input. That's a user-code decision. If Django > strips out data I wanted, there's nothing I can do to get it back.
I concur. The consensus seems to be shifting towards a 'strip' flag though (defaulting to false), and I'm +1 on that. That would make it explicit, minimise repetitive boilerplate code and also make it less likely to accidentally forget to strip a field somewhere in the process. Maybe a revisit to this related ticket is in order? https://code.djangoproject.com/ticket/4960 > Jacob > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-developers@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
