uv: An extremely fast Python package and project manager, written in Rust

(github.com)

741 points chirau | 1 comments | 23 Jun 25 16:27 UTC | HN request time: 0.431s | source

Show context

acheong08 ◴[23 Jun 25 18:56 UTC] No.44358882[source]▶

Just a few months back I said I would never use uv. I was already used to venv and pip. No need for another tool I thought.

I now use uv for everything Python. The reason for the switch was a shared server where I did not have root and there were all sorts of broken packages/drivers and I needed pytorch. Nothing was working and pip was taking ages. Each user had 10GB of storage allocated and pip's cache was taking up a ton of space & not letting me change the location properly. Switched to uv and everything just worked

If you're still holding out, really just spend 5 minutes trying it out, you won't regret it.

replies(11): >>44359172 #>>44359456 #>>44359522 #>>44359897 #>>44359946 #>>44360000 #>>44360262 #>>44360544 #>>44360813 #>>44361022 #>>44363908 #

_vya7 ◴[23 Jun 25 20:51 UTC] No.44359946[source]▶

>>44358882 #

I remember using pip and venv back in like 2009. Last time I checked, maybe 5 or 10 years ago, the recommendation of the community was generally to just use Docker instead of all these tools. Did that not catch on?

replies(3): >>44360117 #>>44361988 #>>44364932 #

1. dagw ◴[24 Jun 25 11:20 UTC] No.44364932[source]▶

>>44359946 #

Docker solves a different problem. Docker is a way to basically ship your whole OS off to another machine. You still have to have a way to install the right version of python and all the python libraries you need inside the Docker container, and uv is great for this.

Secondly Docker only solves a subset of problems. It's fine if you're developing a server that you will be deploying somewhere. It's inconvenient if you're developing an end user application, and it's completely useless if you're developing a library you want people to be able to install.

↑