←back to thread

741 points chirau | 4 comments | | HN request time: 2.066s | source
Show context
polivier ◴[] No.44358512[source]
The first time I used `uv`, I was sure that I had made a mistake or typed something wrong because the process finished so much more quickly than anything I had ever experienced with `pip`.
replies(4): >>44358523 #>>44358606 #>>44358689 #>>44359058 #
tux3 ◴[] No.44359058[source]
I've sometimes had uv take up to 200ms to install packages, so you could feel a slight delay between pressing enter and the next shell prompt

You don't have that problem with Poetry. You go make a cup of coffee for a couple minutes, and it's usually done when you come back.

replies(1): >>44359551 #
1. Numerlor ◴[] No.44359551[source]
It's funny when the exact same thing was probably said about pipenv and poetry
replies(1): >>44361014 #
2. icedchai ◴[] No.44361014[source]
I've had poetry sit there for minutes resolving dependencies at a previous company. I thought something was broken... it probably was... but it did eventually complete.
replies(1): >>44374334 #
3. projectdelphai ◴[] No.44374334[source]
I've had poetry take so long that I've just deleted the whole cache/poetry list and reinstalled the packages rather than wait for poetry to figure out whatever dependency hell it found itself in. I switched to uv the minute i tried it out
replies(1): >>44377483 #
4. icedchai ◴[] No.44377483{3}[source]
lol. Yes, I've done the same thing. haha. I couldn't do that at a previous company cause they were pretty anal about mass updates to poetry.lock