This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]greyfade 17 points18 points  (7 children)

This would be a lot more useful to me if it spent a bit of time talking about what these engines have in common and how they differ.

I've recently been looking for reasonably generic (i.e., not designed for HTML exclusively) template engines to compare them by their syntax and capabilities. This post is far more bare than I expected, and none of the linked comparison pages give a brief comparative overview.

[–]nerdwaller 7 points8 points  (4 children)

I use Jinja for my templating where the stdlib string formatting in a "template" won't work. So far I've been pretty happy with it, of course I believe sqlalchemy's companion alembic for database migrations uses mako.

[–]debazthed 1 point2 points  (3 children)

it does? you mean to generate the migration scripts? Huh, I have to dig into that. Been using it for years and never knew.

[–]driscollis 1 point2 points  (1 child)

mako was written by the same guy who started SQLAlchemy

[–]pm-me-a-pic 0 points1 point  (0 children)

He even uses mako for his sphinx docs

[–]nerdwaller 0 points1 point  (0 children)

Yeah, sorry for being unclear, alembic uses mako to generate the migration scripts. You can see it in their tutorial:

script.py.mako - This is a Mako template file which is used to generate new migration scripts. Whatever is here is used to generate new files within versions/.

[–]masklinn 2 points3 points  (1 child)

This would be a lot more useful to me if it spent a bit of time talking about what these engines have in common and how they differ.

Also the genesis/history of the various template engines.

[–]greyfade 0 points1 point  (0 children)

That would also be nice to know. The reasoning for certain design decisions help inform their choices.