Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Pipenv installed using Linuxbrew doesn't work anymore
See original GitHub issueIssue description
Since last updating pipenv through Homebrew for Linux, I get the following error each time I try to use it:
/home/linuxbrew/.linuxbrew/Cellar/pipenv/2018.11.26_4/libexec/bin/python3.8: error while loading shared libraries: libpython3.8.so.1.0: cannot open shared object file: No such file or directory
Expected result
I would expect pipenv to run normally.
Actual result
The only thing I get is the error above.
Steps to replicate
Update pipenv through $ brew update; brew upgrade. Next time I try to run pipenv it gives me the error above.
Even $ pipenv --support fails so I have nothing to add.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yes, I’ve noticed it too when I did a
brew update && brew upgradethis morning. My experience from last time is that they usually notice such issues at Homebrew within a day, and push an update that solve them quickly. But it’s annoying. I think it might make more sense to create an issue over at the Linuxbrew-core repo, but their requirements to fill in an issue are so complex I actually decided to wait it out for now. Feel free to create an issue there if you have the energy!Homebrew/linuxbrew-corerepository is marked read only. This issue feels outdated.