3 ms·
I assume for things like templating emails. Or configuration files for deployment. That's at least what I've used it for. It's handier and more straight-forwar
by spamizbad 13y ago
I assume for things like templating emails. Or configuration files for deployment. That's at least what I've used it for.
It's handier and more straight-forward than using Django's templating engine.
- oinksoft 13y agoI thought he might have meant that, but I never had too much difficulty doing this through the Django template API.
- falcolas 13y agoIt's not bad, but the Jinja2 language is more expressive, and the API is a bit better. Not enough we would migrate away from Django templates to it, but enough to not migrate away from Jinja.
- oinksoft 13y agoFair enough, I tend to use something very restrictive like Django templates (I made/use an Erlang port of the language as well: https://github.com/oinksoft/dtl https://github.com/oinksoft/dtl) or something very flexible like Mako if I have the choice and need it.