-
-
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
pipenv 2018.11.14 fails with "Not a valid python version" when installed via pip on a system that has Python 2.7 #3294
Comments
python3
is on the path
Getting the same error while running I unistalled it, and re-installed a previous release:
and this is now working again on my system. I believe the issue here is that the latest Not sure how to make it work (i.e., make it so that the
└─( pipenv --python 3.6 installCreating a virtualenv for this project… Pipfile: /home/marco/workspaces/main/serverless/python/Pipfile Using /usr/bin/python3.6 (3.6.7) to create virtualenv… ⠇Running virtualenv with interpreter /usr/bin/python3.6 Using base prefix '/usr' New python executable in /home/marco/.virtualenv/python-AO51eeIn/bin/python3.6 Also creating executable in /home/marco/.virtualenv/python-AO51eeIn/bin/python Installing setuptools, pip, wheel...done. |
It looks like |
I'll have the last bugfix before the release up and building, but yeah, this is another pythonfinder issue unfortunately -- it's fixed in master but not released yet. I'm going to close this for now (you'll be able to fix by upgrading in a few hours), sorry for the trouble! P.S. You should avoid using |
Hey - super-thanks for jumping on this one so quickly, appreciated! Absolutely no trouble, I'll update my version once it's ready.
No kidding! I'm always super-careful with the system distro, which is why is have been using virtualenv and now pipenv; unfortunately, it's a bit of a catch-22: in order to use either, they need to be installed on the system python; I only upgrade (manually, via |
Facing this problem 2 years later on a windows computer. First it told me that Anaconda3 wasn't a valid python path. Then I installed Anaconda and it told me that 2.7 wasn't a valid python path. What finally worked for me was massenz's solution to just install the older version of pipenv: |
Using pip install pipenv==2018.10.13 like Wyzzard123 mentioned fixed the problem for me. I was stuck in Anaconda3 not being a vlid python path before |
I'm still encountering this issue on |
Issue description
When I run this:
pipenv --python 3.6 install
it fails even if both
python3
andpython3.6
are on thePATH
:Expected result
pipenv
should be sufficiently smart to figure it out by itself thatpython3.6
is the desired binary.Actual result
This is the error, full stacktrace at the bottom:
Steps to replicate
See below.
Please run
$ pipenv --support
, and paste the results here.$ pipenv --support
Pipenv version:
'2018.11.14'
Pipenv location:
'/usr/local/lib/python2.7/dist-packages/pipenv'
Python location:
'/usr/bin/python'
Python installations found:
(and, LoL -
--support
fails with the same error)Full Stacktrace
The text was updated successfully, but these errors were encountered: