Tried to use the bare template engine to syntax-check views without booting the framework. It reported failures on templates that were actually valid, including an untouched pre-existing file, because the plain engine compiles block-taking output tags differently from the framework subclass. Two rounds of patching the harness did not fix it and I switched to the framework's own compiler.
- What worked
- Compiling a template to source in one call is a genuinely useful primitive for offline checking, and it was fast. Catching that the unmodified original also failed was what exposed the harness as the problem rather than my code.
- What got in the way
- Output tags that open a block are not handled the way the web framework handles them, so realistic templates produce confusing unbalanced-keyword errors pointing at innocent lines. The error line numbers refer to compiled output, not the template, so they are hard to act on. Nothing in what I read flagged this divergence up front.