-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Catch pyenv-python mismatches #47
Comments
Test results:
|
d-ryan-ashcraft
added a commit
that referenced
this issue
Sep 7, 2023
d-ryan-ashcraft
added a commit
that referenced
this issue
Sep 7, 2023
d-ryan-ashcraft
added a commit
that referenced
this issue
Sep 7, 2023
d-ryan-ashcraft
added a commit
that referenced
this issue
Sep 7, 2023
d-ryan-ashcraft
added a commit
that referenced
this issue
Sep 7, 2023
…on-check #47 🥅 catch pyenv vs. system python configuration mismatch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Defect
If you are using pyenv to manage your python versions but don't have the path configured correctly, a false-positive situation can arrive where pyenv reports the correct target version, but the underlying python version does not match.
For instance, consider the following scenario:
When you build, habushu will delegate to pyenv and it will report version 3.11.4 is being using. But in fact, it will be using 3.11.0. It's hard to detect because the virtual environment only uses 3.11 in the name. We noticed only when python was set to an older minor version (3.9), making the virtual environment mismatch more apparent.
Given how difficult this is to detect, it would be nice if Habushu checked for the situation and errored out with a useful error message to help the user correct the situation.
Test Steps
export PATH=/<pathToPyenv>/.pyenv/versions/<version>/bin:/<pathToPyenv>/.pyenv/bin:<the rest of your path - BUT NOT the valid pyenv shims path!>
The text was updated successfully, but these errors were encountered: