-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
"The Python interpreter can't be found" error when running pipenv install --system
with a python3 but no python
#5261
Labels
Type: Bug 🐛
This issue is a bug.
Type: Regression
This issue is a regression of a previous behavior.
Comments
jfly
added a commit
to jfly/pipenv
that referenced
this issue
Aug 16, 2022
This fixes pypa#5261. Before this change, I would get a "The Python interpreter can't be found" error when running `pipenv install --system` with a python3 but no python. Demo: ``` $ docker run $(docker build -q -f Dockerfile.pipenv-2022.8.15 https://github.com/jfly/2022-08-16-pipenv-system-which-issue.git#main) Installing dependencies from Pipfile.lock (63bec0)... The Python interpreter can't be found.▉ 0/4 — 00:00:00 🐍 ▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉ 0/4 — 00:00:00 ``` I'm confident this bug was introduced in pypa@f276360, which removed a usage of `first()`, but broke the "filter None values" behavior that `first()` gave us.
jfly
added a commit
to jfly/pipenv
that referenced
this issue
Aug 16, 2022
This fixes pypa#5261. Before this change, I would get a "The Python interpreter can't be found" error when running `pipenv install --system` with a python3 but no python. Demo: ``` $ docker run $(docker build -q -f Dockerfile.pipenv-2022.8.15 https://github.com/jfly/2022-08-16-pipenv-system-which-issue.git#main) Installing dependencies from Pipfile.lock (63bec0)... The Python interpreter can't be found.▉ 0/4 — 00:00:00 🐍 ▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉ 0/4 — 00:00:00 ``` I'm confident this bug was introduced in pypa@f276360, which removed a usage of `first()`, but broke the "filter None values" behavior that `first()` gave us.
2 tasks
Thanks for your report. I am also running into this problem with python3.8 and pipenv==2022.8.15 . |
matteius
added
Type: Regression
This issue is a regression of a previous behavior.
Type: Bug 🐛
This issue is a bug.
labels
Aug 16, 2022
matteius
pushed a commit
that referenced
this issue
Aug 16, 2022
* Actually filter out missing interpreters This fixes #5261. Before this change, I would get a "The Python interpreter can't be found" error when running `pipenv install --system` with a python3 but no python.
yeisonvargasf
pushed a commit
to yeisonvargasf/pipenv
that referenced
this issue
Nov 19, 2022
* Actually filter out missing interpreters This fixes pypa#5261. Before this change, I would get a "The Python interpreter can't be found" error when running `pipenv install --system` with a python3 but no python.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Type: Bug 🐛
This issue is a bug.
Type: Regression
This issue is a regression of a previous behavior.
Issue description
I get a "The Python interpreter can't be found" error when running
pipenv install --system
with a python3 but no python.Demo:
I'm confident this bug was introduced in f276360, which removed a usage of
first()
, but broke the "filter None values" behavior thatfirst()
gave us.The text was updated successfully, but these errors were encountered: