On 9 Jul 2011, at 10:44, Sam Lai wrote: > 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
I'm on the fence here, I like the idea of a strip flag, but I do agree that it seems too specific. Perhaps something more generic, eg: myfield = models.CharField(max_length=255, text_filters=[StripFilter, UpperFilter]) The filters would chain into each other. I'm not sure I like the syntax though, seems a bit ugly. I do like the elegance of just having a strip flag. - Andy -- 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.
