I’ve got a couple small (500 or 600 lines of template code) Django sites, and I’d like to migrate them to using Jinja2… But I’d like to get some idea of how much work it will be. So, in general, about how much work is it to migrate a small Django site to Jinja2? And is it “worth it”?
Share
While it’s just my own experience, I found converting from Django to Jinja2 to be worthwhile for the following reasons:
Jinja2 gives significantly more helpful error output than Django (i.e. traces to the line number in the template where the error occurred).Edit: According to Dor’s comment, Django gives helpful error messages that point to the line and context of a problem, much like Jinja2.If you haven’t had any trouble with Django’s template engine, Jinja2’s should feel relatively intuitive, if perhaps a bit more polished (or it did to me, at any rate). As well, I found the
Coffinproject well written and reasonably helpful when converting from Django to Jinja2 – both for its use, and as an example of how to extend Jinja2.All that being said, Django’s template engine is solid and quite capable for most tasks. I believe it’s being improved in the next revision of Django, and there is quite a lot of effort to add to its capabilities by quite a number of dedicated developers. As a result there are no worries of it becoming unsupported in the near to medium-term future.
Again, that’s just my experience, for what it’s worth – I hope that’s helpful.