Comment 11 for bug 1860369

The scope of the issue does not appear to be limited to python. See `printpath` in the the example linked above to see that a simple binary executable has the incorrect path.

In the meantime, here is a proposal for snapcraft to _always_ generate the snapcraft-runner (inserted into the command-chain), which does appear to workaround the issue. https://github.com/snapcore/snapcraft/pull/2889

The difference here is that the snapcraft-runner will effectively just no-op in the cases where it wasn't generated before. Not ideal, but can be removed later when a proper fix becomes available.