Fixes #6411. The fix here was to adjust the existing shebang rewriting infrastructure to input an absolute path instead of hinging upon `env`, which was resolving Python interpreters in the wrong order. The spread test changes ensure this works by forcing execution through the shebang instead of going the "easy route" and invoking the app with Python. An open question I have is regarding documentation. Should this even be documented? It's a difference between core24 and core26 Python snaps, but it doesn't affect the uv plugin (doesn't rewrite shebangs in the first place, no need!) and so it can't easily be inserted into `_python_common.rst` as it exists today. I think that most people shouldn't bump into this issue though, because they've either patched the problem themselves, were already invoking with `python`, or the snap was just simply broken. --- - [ ] I've followed the [contribution guidelines](https://github.com/canonical/snapcraft/blob/main/CONTRIBUTING.md). - [ ] I've signed the [CLA](http://www.ubuntu.com/legal/contributors/). - [ ] I've successfully run `make lint && make test`. - [ ] I've added or updated any relevant documentation. - [ ] In documents I changed, I [added a meta description](https://canonical-starflow.readthedocs-hosted.com/how-to/add-a-page-meta-description/) if one was missing. - [ ] I've updated the relevant release notes.