Hacker News Reader

A) The template system rocks

B) Use PISTON for APIs: he could have had it working WAY easier

C) Use SOUTH with the ORM. The ORM wouldn't make much sense on its own unless you like wiping your database a lot during development.

http://ericholscher.com/tag/largeproblems/ "Large Problems in Django: Mostly Solved"

It is a shame the tutorial doesn't point out South and Piston, everyone should be using them.

View on HN

The template system rocks if you like handcuffs on your templates - and for some projects that may be the case.

Otherwise it's crippled in comparison to Jinja or Mako - with large amounts of un-Pythonic boilerplate if you want to write template tags.

To an extent you can replace it but again you will have trouble with those "reusable" apps.

I think it's better to keep additional logic in your page view functions instead of letting it bloat the template html. Why use a two pass method to parse your custom template logic into python code when you can just write the python code in the view functions?

Reply on news.ycombinator.com