Any package requiring importlib-metadata breaks locking
See original GitHub issueThe most recent version of importlib-metadata
is 2.0.0. This is the version that gets resolved when any package is installed that required importlib-metadata
without an upper bound. For example: flake8
.
The virtualenv
library requires importlib-metadata < 2.0
.
When project.get_environment()
is called the dependencies for virtualenv
are compared to the working set resolved for the Pipfile dependencies and a VersonConflict error is raised.
This is a very frustrating error because doing pipenv lock -v
gives no indication of which package requires importlib-metadata < 2.0. Also inspecting pipenv graph
gives no indication either.
A temporary fix would be to pin importlib-metadata == "1.7.0"
in the Pipfile.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:46
- Comments:19 (1 by maintainers)
Top Results From Across the Web
Using importlib.metadata — Python 3.11.1 documentation
importlib_metadata is a library that provides access to the metadata of an installed Distribution Package, such as its entry points or its top-level...
Read more >What Causes Brake Lock-Up - Les Schwab
There is a long list of reasons that one or all of the brakes on your vehicle might lock up. These can include...
Read more >Sinking brake pedal/front brakes locking up on their own when ...
No Charging Required Car Jump Starter: https://amzn.to/2CthnUU 6. Battery Pack Car Jump Starter: http://amzn.to/2nrc6qR 7.
Read more >Why Do Brakes Lock Up? - BuyBrakes
Locking brakes are most common when drum brakes are involved, but it can also happen with disc brakes. As with any mechanical system, ......
Read more >What Causes Brakes to Lock Up? | Ira Subaru Danvers MA
Our service technicians will provide brake repair, including any necessary comprehensive fixes for the ABS system. If you have any questions for us,...
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
With
pip install -U pipenv
was solved for me.The workaround of deleting the
Pipfile.lock
file and then re-runningpipenv lock
always seems to work but here is what I did for a more permanent fix.pipenv --rm
brew uninstall pipenv
pip install -U virtualenv
pip install --user pipenv
pipenv install
Repeat runs of
pipenv lock
work as expected and do not re-trigger the conflict error message.