running pipenv by itself is slow
See original GitHub issueI don’t know if this is feasibly debuggable, or if this is even a bug.
I run pipenv
to get its help page, and it takes a surprisingly long time to show output. Here’s the results of one time pipenv
. Multiple runs gave similar results.
pipenv 0.79s user 0.12s system 99% cpu 0.912 total
Seems like it should be instantaneous to run what’s essentially a help page.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:18 (18 by maintainers)
Top Results From Across the Web
Is Python's pipenv slow? - Stack Overflow
Yes, I've found pipenv's locking and dependency resolution is terrible. For what it's worth, I've moved to just venv and poetry.
Read more >Frequently Encountered Pipenv Problems - Read the Docs
Run pipenv lock --clear and try again. The lock sequence caches results to speed up subsequent runs.
Read more >Making pip installs a little less slow - Python⇒Speed
Installing packages with pip, Poetry, and Pipenv can be slow. Learn how to ensure it's not even slower, and a potential speed-up.
Read more >Pipenv: promises a lot, delivers very little | Chris Warrick
This is one of Pipenv's notable issues: it's slow. Of course, this isn't the only one, but it defintely doesn't help.
Read more >Pipenv review, after using it in production : r/Python - Reddit
It runs under a single python version and that's that. ... This turned out much longer the expected so TLDR; pipenv is slow...
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
@uranusjr good point. I thought to address those costly imports as close as possible to the origin, so as to fix performance in more places.
It turns out there are but a few places making imports lazy would speed up things significantly, and there are clear traces of past improvements, so probably it was newer changes that were made without lazy imports in mind that reintroduced the slowdowns.
I’ve posted a PR to address those: https://github.com/pypa/pipenv/pull/1917
I believe we went down this road in the past and it broke many things. If you can get it to work nobody will say no, but I just want to warn you before you invest your time that it will probably be frustrating