Comments on: Django round 2

By: versa106

versa106 — Mon, 09 Feb 2009 02:59:23 +0000

thanks!

By: mike bayer

mike bayer — Mon, 08 Sep 2008 08:20:56 +0000

web designer doesn't need to learn Python just because there's some python in the template – this is a common overreaction to a problem that doesn't really exist. I wrote an old rant about this here: http://techspot.zzzeek.org/?p=3

By: justin

justin — Sat, 06 Sep 2008 02:26:50 +0000

I disagree. I think that content should be provided by the controller, but things that have to do with the look should be provided by the template.

In one project, I have a base that every template inherits from. There are some basic view things that it figures out. Like if it's a mac, do one thing, if it's a PC, do another. I don't want to pass this display data with actual content every time, it's much better if the template just figures it out itself.

By: Alex Yakovlev

Alex Yakovlev — Sat, 06 Sep 2008 01:46:39 +0000

Hello.

This will do:
{% for ping in object.pingback_set.all %}

Current time, the name of the file, etc. – just pass them into a template as variables if you need them.
Web designer is not supposed to learn Python to create a template, programmer will make available any variables/info to her

By: justin

justin — Fri, 05 Sep 2008 19:13:38 +0000

I agree that you shouldn't use python in your templates, but there is a limit to this. For instance, lets say I wanted to print every pingback for a blog entry. I should be able to do something like:

{% for ping in object.pingback_set.all() %}

You can't do something as simple as this in the django template engine. There are other instances where arbitrary python is nice. Let's say you want to put the current time on the page. Or set the title to the name of the file. All these things benefit from being able to execute normal python, and are not outside the realm of the template engine.