Other neat tricks is to use uvx (uv equivalent of npx) to run one time commands in some contexts:
- alias download_mp3="uvx --no-cache --from yt-dlp[default] yt-dlp --extract-audio --audio-format mp3" to download sound from Youtube videos, SoundCloud pages, etc. This update yt-dlp every time, which is required given the counter measures change so often and the dl rarely affect the total processing time anyway (requires ffmpeg).
- "uvx --with <package> --with pyqt5 --from qtconsole jupyter qtconsole" starts a qtconsole (GUI version of ipython) with <package> installed so you can test it quickly. Temp venv, everything cached so next time it's instant, one single copy of pyqt5 for the current use no matter how many times you run those.
- "uvx --with virtualenv pipx run pipsi install nodejs-bin". Ok it's useless, but it's fun that it even works :)
While neat, doesn't it also comes with certain issues?
Startup times has to be slower, but probably only for the first run?
There's a some level of violation of the "Principle Of Least Surprise", depending on the setting. For some it will be the reverse, the script they got just works, without any setup or package installation. For others we'll wonder why it just started downloading a bunch of packages we already have.
Probably not the greatest idea for production environments, where you should not or can not just pull in packages from the internet.
It's really cool that it works, but I think I'd recommended using it highly selectively.
I've been using this for a few weeks now, and it's really handy. But I did learn the hard way that it fails if you don't have internet connection, even if you already have the venv cached.
It's a neat trick, but it still depends on uv being installed and network connectivity.
What's the advantage of this that makes it worth despite these constraints, compared to e.g. using pyinstaller [1] to build and distribute a single executable file with the python interpreter and all the dependencies of your project bundled in it in the exact versions you chose in your development virtual environment?
Zx adds a couple nice ease of use things to node.js, designed to help shell scripting. Among other things, if you call /usr/bin/env zx, it will automatically retrieve any module imports you have in your code! https://github.com/google/zx
Other neat tricks is to use uvx (uv equivalent of npx) to run one time commands in some contexts:
- alias download_mp3="uvx --no-cache --from yt-dlp[default] yt-dlp --extract-audio --audio-format mp3" to download sound from Youtube videos, SoundCloud pages, etc. This update yt-dlp every time, which is required given the counter measures change so often and the dl rarely affect the total processing time anyway (requires ffmpeg).
- "uvx --with <package> --with pyqt5 --from qtconsole jupyter qtconsole" starts a qtconsole (GUI version of ipython) with <package> installed so you can test it quickly. Temp venv, everything cached so next time it's instant, one single copy of pyqt5 for the current use no matter how many times you run those.
- "uvx --with virtualenv pipx run pipsi install nodejs-bin". Ok it's useless, but it's fun that it even works :)
uv's cache system and downloads optimization are quite smart, as Charlie marsh (astral CEO) explains in the interview: https://www.bitecode.dev/p/charlie-marsh-on-astral-uv-and-th...
While neat, doesn't it also comes with certain issues?
Startup times has to be slower, but probably only for the first run?
There's a some level of violation of the "Principle Of Least Surprise", depending on the setting. For some it will be the reverse, the script they got just works, without any setup or package installation. For others we'll wonder why it just started downloading a bunch of packages we already have.
Probably not the greatest idea for production environments, where you should not or can not just pull in packages from the internet.
It's really cool that it works, but I think I'd recommended using it highly selectively.
> Probably not the greatest idea for production environments
Nor for any system where one takes care to not needlessly increase the threat surface.
I have been doing this for a while. Voila:
#!/usr/bin/env -S uv run -q --no-project --python ">=3.12" --with "openai"
I've been using this for a few weeks now, and it's really handy. But I did learn the hard way that it fails if you don't have internet connection, even if you already have the venv cached.
`--offline` :)
That's really unexpected! I'd default to the assumption that it would "just work" if all the dependencies are already met.
It's a neat trick, but it still depends on uv being installed and network connectivity.
What's the advantage of this that makes it worth despite these constraints, compared to e.g. using pyinstaller [1] to build and distribute a single executable file with the python interpreter and all the dependencies of your project bundled in it in the exact versions you chose in your development virtual environment?
[1] https://pyinstaller.org/
Can just share a clear text script with a colleague over slack and let him just run it without extra steps.
this builds upon PEP 723, which is "accepted", so it's likely here to stay.
https://peps.python.org/pep-0723/
I've been very slowly migrating scripts to work with this, and `pipx run`. glad to know uv has also picked it up.
reminds me of nix-shell shebang [0] which enables a similar pattern for scripts of arbitrary languages.
[0]: https://nixos.wiki/wiki/Nix-shell_shebang
Maybe surprisingly, JBang has offered this functionality for Java since 2020. Happy we have it un Python too, now.
Zx adds a couple nice ease of use things to node.js, designed to help shell scripting. Among other things, if you call /usr/bin/env zx, it will automatically retrieve any module imports you have in your code! https://github.com/google/zx
Curious - how many containers and machines images these days come with uv by default?
Doesn't look like my Ubuntu machine comes with 'uv' installed at least. Can't say I've ever heard of it either.
It's the new hotness in Python package management:
https://docs.astral.sh/uv/
https://xkcd.com/1987/
https://xkcd.com/927/
`uv` is not a new standard though, just a wrapper.
Fantastic. I'm very impressed with Simon Willison in general (what a dynamo) and this in particular.
Simon is an impressive individual, but in this instance, you're praising the messenger and not the source.
> Code from this PR [1] by David Laban.
That leverages the features of uv run with embedding script dependencies [2].
[1] https://github.com/alsuren/sixdofone/pull/8 [2] https://docs.astral.sh/uv/concepts/projects/run/#running-scr...