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
Issue after upgrading python to 3.7 #2775
Comments
I am having a similar issue - where arch linux upgraded from 3.6.5 to 3.7 and now I get an error whenever I try to run pipenv. What works for me, but it is indeed a bit of an ugly hack, is to first upgrade pip, reinstall pipenv and for every repository using pipenv, erase the virtualenvironment and recreate it. rm -rf `pipenv --venv`
pipenv install --dev and this seems to do the job. Note: you should also probably change the requirement in the Pipfile from python 3.6 to 3.7. I hope this helps, but I'm also wondering if there is a more robust solution... |
That is related to how Homebrew configures Python. There is nothing Pipenv (or any Python libraries) can do about it. DO NOT install things on a Homebrew Python if you don’t want this to happen. If it does, re-installing is your only option. I remember I commented on a similar issue a few days ago, but couldn’t find it at the moment :( |
@uranusjr Isn't this recommended by the docs though? |
Yes, so? |
Homebrew installs are kind of complicated and outside of our control, you assume some risk if you use them (neither of us uses a Mac so we really can't offer much insight on that) |
what worked for me was |
What worked for me was just nuking all my envs: @omrihar why the Edit: using brew-installed pipenv (2018.11.26_2) w/ python3.7. I was having issues at the locking phase of install, e.g. |
what helped to us was: $ brew uninstall pipenv
$ brew install python3.6
$ pip3 install --user pipenv
$ mkdir -p ~/bin
$ ln -s ../Library/Python/3.6/bin/pipenv ~/bin/ and if you didn't do so yet, add ~/bin/ to your PATH by editing the PATH line in ~/.bash_profile:
Don't forget to close and open shell |
I was running into this issue, and solved it by running according to the docs
|
I ran into the same issue after upgrading OSX version. Solved by uninstalling homebrew installation and then following the "Pragmatic Installation" instructions:
Don't forget to add the user base’s binary directory to your PATH per the instructions. |
Hi, i'm getting the same errors, but i'm not sure what I need to uninstall and how. Trying to uninstall python@3.8 did not work since awscli depends on it, which doesn't make sense if it wasn't installed before... What do I generally need to uninstall to solve this issue? thanks for your help. |
Uninstalling python did the trick. thanks |
Issue description
I'm on a Mac and installed
pre-commit
usingbrew
and without even asking for it got upgraded from python 3.6.5 to 3.7. (3.6.5 was also under the control ofbrew
)Now pipenv fails with "Library not loaded"-error.
Expected result
Pipenv to work as before the python upgrade.
Actual result
Comments
What's the proper way of fixing the issue? Can I edit some config-file to point to 3.7 instead?
Could
pipenv
perhaps be more lenient and rely on thepython3
binary instead of thepython3.6
?The text was updated successfully, but these errors were encountered: