Workaround for jinja substitutions in code blocks

[OriolAbril]

Hi,

We have an example gallery of PyMC usage, built with sphinx from jupyter notebook examples. Most notebooks depend on pymc+optional dependencies only so the install needed for this to work is the same for all, but some have extra dependencies to show for example integration of pymc with fenics or keras.

I was thinking about writing down a small installation.md that we could then include in the relevant files that would have a couple sentences about the need for extra installs and the conda/pip (or both with tabs) commands that should be executed. As those external dependencies change from notebook to notebook, I thought we could use jinja substitutions to cover that:

• define myst substitutions in frontmatter -> we'd define 1-2 keys in our style guide to use i.e. extra_installs
• include the installation.md that has a substitution for extra_installs and should use the one defined in the frontmatter (I think)

However, we can use pip install {{ extra_installs }} as it won't be substituted. Is there any workaround? Maybe some clever jinja operations like take extra_installs prepend pip install and encase between backticks? Should we try to define a myst specific directive/role for "code with substitutions"?