Files
matrix-docker-ansible-deploy/bin
Slavi PantaleevandClaude Opus 5.5 415d784ca0 Find Ansible's interpreter also behind python-exec and wrapper scripts
On Gentoo, the shebang of `ansible-playbook` is the python-exec
dispatcher (`#!/usr/bin/python-exec2c`), which bin/ansible-python.sh
took for an interpreter, because its name starts with `python`.
python-exec only runs the programs it wraps, so every `just run…`
recipe failed with "no python-exec wrapped executable found".

Now only names like `python`, `python3` or `python3.14` are trusted.
For anything else (python-exec, wrapper scripts as on Nix), Ansible is
asked which interpreter it runs on (`ansible-playbook --version`),
before falling back to `python3`, which may lack PyYAML (e.g. in an
active virtualenv).

Same as https://github.com/mother-of-all-self-hosting/mash-playbook/commit/a685940a

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-25 13:33:34 +02:00
..
2026-08-27 18:02:53 +03:00