(docs.astral.sh)

167 points charliermarsh | 1 comments | 19 Nov 24 21:59 UTC | HN request time: 0.226s | source

Show context

alex_suzuki ◴[20 Nov 24 10:11 UTC] No.42192428[source]▶

In a nutshell, what do I gain from switching to uv from my current workflow, which is: 1) create a venv (`python3.xx -m venv venv`) 2) install packages from a requirements.txt into that venv?

One limitation I know of are the inability to detect stale packages.

Apart from „blazing fast“, which I‘m not convinced it really matters to me as I rarely touch the dependencies, what are the main reasons why uv is gaining traction?

replies(4): >>42192436 #>>42192507 #>>42192711 #>>42198294 #

1. imjonse ◴[20 Nov 24 10:57 UTC] No.42192711[source]▶

>>42192428 #

One reason is that it is not just for project venv/deps management but can replace other tools like pipx and pyenv for most scenarios.

↑

Using uv with PyTorch