←back to thread

741 points chirau | 3 comments | | HN request time: 0s | source
Show context
acheong08 ◴[] 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 #
tomjakubowski ◴[] No.44360262[source]
The absolute killer feature for me of uv is that it's still compatible with all of my old venv-based workflows. Just run `uv venv`.
replies(2): >>44363808 #>>44366025 #
1. level09 ◴[] No.44366025[source]
Unfortunately uWSGI (one of the most important libraries) is fundamentally incompatible with uv. had to roll back all my apps that use custom uWSGI for that reason.
replies(2): >>44367841 #>>44403074 #
2. iFreilicht ◴[] No.44367841[source]
Could you explain how? Does it do something funky in the venv that uwsgi doesn't understand?
3. tadaima ◴[] No.44403074[source]
I am using uwsgi with uv. This is not to say the problems you are facing are not real, but it cannot be a 'fundamental incompatibility' if it is working in my case. Here is an example of a CLI invocation I am using for quick testing:

-- uv run uwsgi --socket 0.0.0.0:8080 --protocol=http -w foo.app:server --processes 2 --threads 2 --stats 0.0.0.0:9191 --