On 26 February 2012 05:55, Joe & Anne Tennies <tenn...@gmail.com> wrote: > While this would be a valid argument if Django templates only rendered HTML, > that is not the only thing it can be used to render.
> The original poster gave a very good example of a text-based email. This is pretty much the only valid use-case: human-readable markup which cares about whitespace. But I don't see how multiline tags help here, as now you have a mix of text that does and doesn't care about whitespace, So when reviewing the template, you can't see the layout. > I could list lots of other formats in which white space must be followed to > even be useful (like .CSV). Please don't use templates to render CSV, that's like using regular expressions to parse XML. Most of data exchange and configuration file formats have libraries to serialize them. So no, that's not a use case. > I have used Jinja2 on multiple occasions to render C code that needed to be > code reviewed. While I have nothing against rendering C code with templates, I pity the person reviewing it - why would you force anyone to review auto-generated code? I'm -1 on this until someone actually provides a patch with no performance hit. Really, we know people fork Django for their private use. If this is such a big deal, we should have at least one person using this in production for a while now and have an excellent quality patch to show. -- Łukasz Rekucki -- 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.