Comments on: Using Jinja With Django http://www.davidcramer.net/code/113/using-jinja-with-django.html A blog about Django, JavaScript, CSS, and general web development. Wed, 20 Aug 2008 15:48:10 +0000 http://wordpress.org/?v=2.6 By: Cassie http://www.davidcramer.net/code/113/using-jinja-with-django.html#comment-19889 Cassie Sat, 17 May 2008 14:29:40 +0000 http://www.davidcramer.net/?p=113#comment-19889 hi David I was wondering if you were the David Cramer from Illinois that is in CYT. DOn't think I'm stalking you I am from CYT and I was wondering if I googled names from CYT they would come up. Just wondering. hi David I was wondering if you were the David Cramer from Illinois that is in CYT. DOn’t think I’m stalking you I am from CYT and I was wondering if I googled names from CYT they would come up. Just wondering.

]]> By: Justin http://www.davidcramer.net/code/113/using-jinja-with-django.html#comment-19718 Justin Sun, 30 Mar 2008 19:51:03 +0000 http://www.davidcramer.net/?p=113#comment-19718 There are a couple of great Jinja features that David left out. First is macros, with support for recursion. Writing template code for producing trees is difficult, making it tempting to produce markup in a view or templatetag. That's a pretty glaring omission on Django's part, IMO. Jinja's loops support recursions too. The second is that with a normal parenthesized parameter syntax, you can pass more than one argument to a filter or method. This is absolutely necessary for for some kinds of filters which in Django have to parse an argument string. The filter syntax is nice looking, but without parentheses it's very limited to a strict left-to-write precedence rule. This also encourages more view logic and templatetags. There are a couple of great Jinja features that David left out.

First is macros, with support for recursion. Writing template code for producing trees is difficult, making it tempting to produce markup in a view or templatetag. That’s a pretty glaring omission on Django’s part, IMO. Jinja’s loops support recursions too.

The second is that with a normal parenthesized parameter syntax, you can pass more than one argument to a filter or method. This is absolutely necessary for for some kinds of filters which in Django have to parse an argument string. The filter syntax is nice looking, but without parentheses it’s very limited to a strict left-to-write precedence rule. This also encourages more view logic and templatetags.

]]> By: Greg http://www.davidcramer.net/code/113/using-jinja-with-django.html#comment-19717 Greg Sun, 30 Mar 2008 19:15:20 +0000 http://www.davidcramer.net/?p=113#comment-19717 I don't see much reason to consider replacing Django's tightly integrated template system with an external, un-official one. The reasons listed in this article are vague and lack any backing. I'm not trying to flame here, but I really don't see what Jinja can do for me that Django can't. I don't think you should ever have Python code or extensive logic in template files, either. Again, no flame intended, but one has to be really careful when telling new (or old) Django developers that something is better when there isn't much here to substantiate that notion. I don’t see much reason to consider replacing Django’s tightly integrated template system with an external, un-official one. The reasons listed in this article are vague and lack any backing.

I’m not trying to flame here, but I really don’t see what Jinja can do for me that Django can’t. I don’t think you should ever have Python code or extensive logic in template files, either.

Again, no flame intended, but one has to be really careful when telling new (or old) Django developers that something is better when there isn’t much here to substantiate that notion.

]]> By: David http://www.davidcramer.net/code/113/using-jinja-with-django.html#comment-19716 David Sun, 30 Mar 2008 13:40:43 +0000 http://www.davidcramer.net/?p=113#comment-19716 Django isn't that much safer than Jinja. Both are fully sandboxed, Jinja just allows you to do more in it than Django, without extra hassle with template tag creation etc.. Django isn’t that much safer than Jinja. Both are fully sandboxed, Jinja just allows you to do more in it than Django, without extra hassle with template tag creation etc..

]]> By: Nick http://www.davidcramer.net/code/113/using-jinja-with-django.html#comment-19715 Nick Sun, 30 Mar 2008 13:37:51 +0000 http://www.davidcramer.net/?p=113#comment-19715 David, I mean that risk of injecting harmful python code into templates is bigger than not to allow python code in templates directly. And again, I don't see any valuable (for me of course) reasons to switch to Jinja. So all others reasons are more subjective than objective. David, I mean that risk of injecting harmful python code into templates is bigger than not to allow python code in templates directly.

And again, I don’t see any valuable (for me of course) reasons to switch to Jinja. So all others reasons are more subjective than objective.

]]> By: Ned http://www.davidcramer.net/code/113/using-jinja-with-django.html#comment-19714 Ned Sun, 30 Mar 2008 12:19:00 +0000 http://www.davidcramer.net/?p=113#comment-19714 If Jinja doesn't do autoescaping, then be very careful. Django's autoescaping is the best thing they've done to improve the security of Django sites in a long time. It prevents human error from creating XSS holes. If Jinja doesn’t do autoescaping, then be very careful. Django’s autoescaping is the best thing they’ve done to improve the security of Django sites in a long time. It prevents human error from creating XSS holes.

]]> By: David http://www.davidcramer.net/code/113/using-jinja-with-django.html#comment-19706 David Sun, 30 Mar 2008 09:30:25 +0000 http://www.davidcramer.net/?p=113#comment-19706 It converts them when the file is initialized, it doesnt do it over and over. And if you're at risk of your template editors hacking your site, then they shouldn't be editing templates.. It converts them when the file is initialized, it doesnt do it over and over.

And if you’re at risk of your template editors hacking your site, then they shouldn’t be editing templates..

]]> By: Nick http://www.davidcramer.net/code/113/using-jinja-with-django.html#comment-19705 Nick Sun, 30 Mar 2008 09:28:44 +0000 http://www.davidcramer.net/?p=113#comment-19705 Hmmm, I really don't see any reasons for me to switch to Jinja. I really like the idea to not write python code in template language. Designer doesn't need to know python. And there is less possibility to hack site via template editing. Converting filters (on-the-fly I think?) doesn't seem a good idea too and kills performance. Hmmm, I really don’t see any reasons for me to switch to Jinja. I really like the idea to not write python code in template language. Designer doesn’t need to know python. And there is less possibility to hack site via template editing.
Converting filters (on-the-fly I think?) doesn’t seem a good idea too and kills performance.

]]> By: David http://www.davidcramer.net/code/113/using-jinja-with-django.html#comment-19699 David Sun, 30 Mar 2008 08:50:58 +0000 http://www.davidcramer.net/?p=113#comment-19699 Baczek, in Jina that could be written as if `user is registered_for event` or `user|is_registered_for(event)` Baczek, in Jina that could be written as if `user is registered_for event` or `user|is_registered_for(event)`

]]> By: Baczek http://www.davidcramer.net/code/113/using-jinja-with-django.html#comment-19698 Baczek Sun, 30 Mar 2008 08:49:02 +0000 http://www.davidcramer.net/?p=113#comment-19698 I write test filters so their name starts with 'is_', e.g.: {% if user|is_registered_for:event %} ... {% endif %} works well and is quite readable. I write test filters so their name starts with ‘is_’, e.g.:

{% if user|is_registered_for:event %} … {% endif %}

works well and is quite readable.

]]>