Originally posted by @bjeurissen in #2047 (comment)

See #2047 and #2215.

D'Oh. Better to discover such while it's only on dev though.

1. We can just revert to #!/usr/bin/env python3, despite the recommendations against use of env;
2. This comment on the page Donald linked earlier suggests using some shell logic within the shebang itself to determine the appropriate interpreter;
3. The recommendation to incorporate into the build system isn't ideal for us given we're now distributing pre-compiled code, i.e. we can't rely on configure or build. If however we had a script that set script shebangs, then configure could use logic of any arbitrary complexity to try to decide this, and those installing from pre-compiled packages could still use it if the default doesn't work on their system.
4. Still not a fan of requiring users to explicitly specify the interpreter each time...
5. Any other options still on the table?