Fix python binary lookup on debian bullseye (11)#240
Open
oxivanisher wants to merge 1 commit intofboender:masterfrom
Open
Fix python binary lookup on debian bullseye (11)#240oxivanisher wants to merge 1 commit intofboender:masterfrom
oxivanisher wants to merge 1 commit intofboender:masterfrom
Conversation
On debian bullseye, the `/usr/bin/python` symlink is [intentionally removed](https://wiki.debian.org/Python#Python_in_Debian) (see the note). With this change, the wrapper detects `python3`, `python2` and `python` symlinks in this order. The error that lead me to this was (added so that searches on github will find this PR): `No suitable python version found (v2.7 or higher required). Aborting`
|
Thanks for the pull request, saved my day under MacOS. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On debian bullseye (now stable), the
/usr/bin/pythonsymlink is intentionally removed (see the note). With this change, the wrapper detectspython3,python2andpythonsymlinks in this order.The error that lead me to this was (added so that searches on github will find this PR):
No suitable python version found (v2.7 or higher required). Aborting