←back to thread

Using uv with PyTorch

(docs.astral.sh)
167 points charliermarsh | 6 comments | 19 Nov 24 21:59 UTC | HN request time: 0.668s | source | bottom
1. paradite ◴[20 Nov 24 06:48 UTC] No.42191360[source]▶
I was just getting used to pipenv and pyenv combo.

Is this worth switching to?

replies(5): >>42191409 #>>42191442 #>>42191833 #>>42192248 #>>42192347 #
2. baggiponte ◴[20 Nov 24 07:00 UTC] No.42191409[source]▶
Absolutely. No second thoughts.
3. jpalomaki ◴[20 Nov 24 07:09 UTC] No.42191442[source]▶
I've been using a combination of pyenv, venv and Poetry in the past.

Now I have switched to uv with new projects. No problems so far. I definitely recommend giving it a go.

4. silvester23 ◴[20 Nov 24 08:29 UTC] No.42191833[source]▶
I would also say absolutely. We've been using pipenv for ~6 years and have managed to build a pretty good workflow around it. But uv is just _so much faster_. So we've started moving everything over to uv and I don't think we'll ever look back.

Migrating is not super hard, we wrote a small script that moves all the information from a Pipfile to a pyproject.toml and it works like a charm.

5. fernandotakai ◴[20 Nov 24 09:43 UTC] No.42192248[source]▶
yes, 100%. it's not only faster, but it makes sense.
6. cbenz ◴[20 Nov 24 09:59 UTC] No.42192347[source]▶
Absolutely. It changed my Python developer life \o/