←back to thread

Fun with uv and PEP 723

(www.cottongeeks.com)
618 points deepakjois | 1 comments | | HN request time: 2.971s | source
Show context
jkingsman ◴[] No.44369910[source]
uv has been fantastic to use for little side projects. Combining uv run with `uv tool run` AKA `uvx` means one can fetch, install within a VM, and execute Python scripts from Github super easily. No git clone, no venv creation + entry + pip install.

And uv is fast — I mean REALLY fast. Fast to the point of suspecting something went wrong and silently errored, when it fact it did just what I wanted but 10x faster than pip.

It (and especially its docs) are a little rough around the edges, but it's bold enough and good enough I'm willing to use it nonetheless.

replies(4): >>44370062 #>>44374562 #>>44375253 #>>44391468 #
lxgr ◴[] No.44370062[source]
Truly. uv somehow resolves and installs dependencies more quickly than pyenv manages to print its own --help output.
replies(2): >>44370440 #>>44371442 #
mikepurvis ◴[] No.44370440[source]
I know there are real reasons for slow Python startup time, with every new import having to examine swaths of filesystem paths to resolve itself, but it really is a noticeable breath of fresh air working with tools implemented in Go or Rust that have sub-ms startup.
replies(4): >>44370568 #>>44370762 #>>44370852 #>>44374512 #
1. theshrike79 ◴[] No.44370762[source]
The "slowness" and the utter insanity of trying to make a "works on my computer" Python program work on another computer pushed me to just rewrite all my Python stuff in Go.

About 95% of my Python utilities are now Go binaries cross-compiled to whatever env they're running in. The few remaining ones use (API) libraries that aren't available for Go or aren't mature enough for me to trust them yet.