-
-
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
Pyenv support broken since version 2018.10.09 ? #3136
Comments
This is fixed in the master branch and will be released shortly, sorry for the issue! |
The issue still exists. Reopen, please. |
Please ensure, that |
The issue still exists and I'd also ask for re-opening. I have the same setup as the OP, although with newer versions of macOs ( Also, |
I have to agree with @jkukul that this issue isn't fixed. I'm on macOS 10.14.6.
It just doesn't work.
And if I remove
...from my Finally,
...seems to work as expected, too. It's just the autodetection of |
It's still broken, I had to use the workaround. |
i have same error |
Note, everything worked as expected for me after installing pipenv from master ( |
Still broken :( |
I had the same issue. @arkanmgerges solution did the trick for me. |
Hi, I'm very newbie with Python and absolutely lost...
what can I do? |
Issue description
It seems that pipenv since version 2018.10.09 cannot detect versions of Python installed by pyenv anymore.
I experienced this issue on Mac OS X 10.13.6 with pipenv and pyenv installed via homebrew using pipenv version 2018.10.9 and also the newest version 2018.10.13 .
Expected result
When calling
pipenv install
pipenv should detect existing versions of Python installed by pyenv. If it doesn't find a Python version as specified in the Pipfile it should start installing the correct Python version via pyenv and then use it to create the virtual environment.Actual result
Despite version 3.6.5 being installed and available with pyenv
and despite having set PYENV_ROOT correctly
pipenv does not recognize this version and tries to install a new version
And if one does install the version pipenv will claim after the installation, that it still cannot find the installed version of python
All this used to work in pipenv 2018.7.1.
Workaround
On Mac OS X if you just recently updated your version of pipenv you can switch to an older version (2018.7.1):
Alternatively you can install Python via pyenv and set the python path manually when creating the virtual environment
Possible cause
I'm not very familiar with the pipenv code base but the following commit seems to have removed adding of pyenv installations to the PATH:
6d7b26a?diff=unified
$ pipenv --support
Pipenv version:
'2018.10.13'
Pipenv location:
'/usr/local/Cellar/pipenv/2018.10.13/libexec/lib/python3.7/site-packages/pipenv'
Python location:
'/usr/local/Cellar/pipenv/2018.10.13/libexec/bin/python3.7'
Python installations found:
3.7.0
:/usr/local/Cellar/python/3.7.0/Frameworks/Python.framework/Versions/3.7/bin/python3.7
3.7.0
:/usr/local/Cellar/python/3.7.0/Frameworks/Python.framework/Versions/3.7/bin/python3.7m
2.7.10
:/usr/bin/python
2.7.10
:/usr/bin/pythonw
2.7.10
:/System/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7
PEP 508 Information:
System environment variables:
PATH
TERM_PROGRAM
PYENV_ROOT
SHELL
TERM
TMPDIR
PIPENV_VENV_IN_PROJECT
Apple_PubSub_Socket_Render
GOOGLE_APPLICATION_CREDENTIALS
TERM_PROGRAM_VERSION
TERM_SESSION_ID
LC_ALL
USER
SSH_AUTH_SOCK
_
PWD
JAVA_HOME
LANG
XPC_FLAGS
XPC_SERVICE_NAME
SHLVL
HOME
PYENV_SHELL
LOGNAME
LC_CTYPE
SECURITYSESSIONID
__CF_USER_TEXT_ENCODING
PYTHONDONTWRITEBYTECODE
PIP_SHIMS_BASE_MODULE
PIP_PYTHON_PATH
Pipenv–specific environment variables:
PIPENV_VENV_IN_PROJECT
:True
Debug–specific environment variables:
PATH
:/usr/local/Cellar/pipenv/2018.10.13/libexec/tools:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
SHELL
:/bin/bash
LANG
:en_US.UTF-8
PWD
:/Users/andreas.maier/git/evonik-1-uc1/backend
Contents of
Pipfile
('/Users/andreas.maier/git/evonik-1-uc1/backend/Pipfile'):Contents of
Pipfile.lock
('/Users/andreas.maier/git/evonik-1-uc1/backend/Pipfile.lock'):The text was updated successfully, but these errors were encountered: