Jürgen Hermann

Another directive that could profit from a `:substitutions:` parameter is `toctree`, my use-case is including generated API docs that have the package name in their path.

See https://github.com/Springerle/py-generic-project/blob/master/%7B%7Bcookiecutter.repo_name%7D%7D/docs/api-reference.rst and imagine the replacement not done by Jinja2 / Cookiecutter, but instead at runtime by the extension.

Well, I have no concrete example, but it is certainly thinkable. OK, I have a maybe contrived one, imagine you want OS-specific versions of a manual, and include dynamic texts...

The first step would be to define the look&feel of such a CLI tool, e.g. ``` sh tablib from ‹in.ext› to ‹out.ext› foobar_yaml | tablib read yaml filter ‹condition› write...

Since I have that role already (but not enough time to do it on top of PR reviews etc), yeah that would work. Let's see if the two original maintainers...

At least on Linux, it is as easy as this: ```console # in a "shiv" working dir $ tar xfz ~/tmp/egenix-pyrun-2.2.3-py3.5_ucs4-linux-x86_64.tgz ./bin/pyrun3.5 $ shiv -e shiv.cli:main -o shiv . $...

```console $ python3 -m this | grep guess In the face of ambiguity, refuse the temptation to guess. ``` If you ask me, `-p` should be a mandatory option. ;)...

BTW, it would be a nice addition security-wise if there were a flag to remove the CWD from `sys.path` on bootstrap, to prevent code injection attacks.

@sdementen Please take a look at #134 if that fits your use-case (not sure it does), with a lesser amount of dark magic.

`./build.sh debian:buster` Unless you have runtime or other non-build problems…