4 ms·
On my system, Pip takes noticeable time just to start up without ultimately doing anything of importance: $ time pip install ERROR: You must give at least
by zahlman 1y ago
On my system, Pip takes noticeable time just to start up without ultimately doing anything of importance:
$ time pip install
ERROR: You must give at least one requirement to install (see "pip help install")
real 0m0.356s
user 0m0.322s
sys 0m0.036s
(Huh, that's a slight improvement from before; I guess pip 25.3 is a bit better streamlined.)
- andy99 1y agolol who is using pip so much that .36s of startup time matters to them? This, if presumably uv can do nothing slightly faster, is an absolutely meaningless benefit
- zahlman 1y ago>who is using pip so much that .36s of startup time matters to them? https://danluu.com/productivity-velocity https://danluu.com/productivity-velocity https://danluu.com/input-lag/ https://danluu.com/input-lag/
- sunshowers 1y agoIn general, whenever you introduce a cache to make software faster (along any dimension), you have to think about cache invalidation and eviction. If your software is fast enough to not need caching, this problem goes away.
- zahlman 1y agoIt's funny because superior caching is also highly relevant to uv's outperformance. (But invalidation/eviction isn't generally a real problem for a cache of installed packages; the cache can be cleaned up whenever and just rebuilt , and the cache has a separate entry per version of a library, where each version is immutable.)
- sunshowers 1y agoAgreed -- the dream of caching is immutability.