Issue after upgrading python to 3.7
See original GitHub issueIssue description
I’m on a Mac and installed pre-commit
using brew
and without even asking for it got upgraded from python 3.6.5 to 3.7. (3.6.5 was also under the control of brew
)
Now pipenv fails with “Library not loaded”-error.
Expected result
Pipenv to work as before the python upgrade.
Actual result
$ pipenv -h
dyld: Library not loaded: @executable_path/../.Python
Referenced from: /usr/local/Cellar/pipenv/2018.5.18/libexec/bin/python3.6
Reason: image not found
Abort trap: 6
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
?
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (3 by maintainers)
Top Results From Across the Web
It's time to stop using Python 3.7
Upgrading to new software versions is work, and work that doesn't benefit your software's users. Users care about features and bug fixes, ...
Read more >Update from python 3.7 to 3.8 causes problems with pylint and ...
The solution to the above-mentioned problems was that a workaround in which every module/package causing problems needed to be uninstalled ...
Read more >Terminal problem after updating python to 3.7 - Ask Ubuntu
I'm running Ubuntu 18.04.4 LTS and encountered an issue where after updating my Python from 3.6 to 3.7.5 my terminal keyboard shortcut ...
Read more >What's New In Python 3.7 — Python 3.11.1 documentation
This article explains the new features in Python 3.7, compared to 3.6. ... The advent of type hints in Python uncovered two glaring...
Read more >python - DEV Community
How to Update Python How to Upgrade to Python 3.7 on Ubuntu 18.04/18.10 · Step 0: Check the current python version · Step...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes, so?
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. I do something like:
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…