Using a Jinja2 variable in an "%include" statement

[hilary.j.oliver]

@funkapus

I’m guessing that what’s going on is that even though the docs said that the Jinja engine goes first, what really goes first is the includes, because maybe the include files have Jinja code in them. If the Jinja engine ran first, and then the includes happened, then Jinja code in the include files would never get acted on. And that makes sense.

Yes you’re right. We should mention this in the docs, where %include is documented, and in the Jinja2 section. (Sorry for that omission!).

Fortunately, Jinja2 has its own template inclusion mechanism to do what you need:

#!Jinja2

{% set inc1 = "include.flow" %}
[scheduling]
...
{% include inc1 %}