Disclaimer: I think part of that previous statement might be biased.
Remember PHP started as a templating language and look where that got us.
There are some similar lingering design decisions which do nothing but make the language uglier and more verbose. Jinja has the same philosophy of not doing evals in the template, but is still quite a bit more pythonic (eg. method calls with arguments, most python objects etc are allowed)
Django's opinionated stance on this helped me to become a better developer. It pushed that stuff back into my views - which in turn made me realise that a lot of the stuff I'd been putting in my views really should be pushed back into a layer below that. It set me on the path to understanding the value of a good separation of concerns.