←back to thread

740 points chirau | 10 comments | | HN request time: 1.239s | source | bottom
1. 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 #
2. baby ◴[] No.44358523[source]
Same here lol! The experience is so smooth it doesn't feel like python
replies(1): >>44359255 #
3. nialse ◴[] No.44358606[source]
Likewise. I was skeptical, then I tried it and won’t go back.
4. augustflanagan ◴[] No.44358689[source]
I just had this same experience last week, and was certain it wasn’t working correctly as well. I’m a convert.
5. 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 #
6. johnfn ◴[] No.44359255[source]
That makes sense, because it's Rust. :)
7. Numerlor ◴[] No.44359551[source]
It's funny when the exact same thing was probably said about pipenv and poetry
replies(1): >>44361014 #
8. icedchai ◴[] No.44361014{3}[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 #
9. projectdelphai ◴[] No.44374334{4}[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 #
10. icedchai ◴[] No.44377483{5}[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