Post

This is so cool. Do you know if it's as simple as uv writing the correct pyproject.toml file for you, or is it doing something more than that?

@nomadicchzherder.bsky.social

If you write the code in the right function in the right file, you don't even need to edit the pyproject.toml. (You need to have a function `main` importable from `mycli`, if I'm not mistaken. To specify a different entry point you'd have to modify the file `pyproject.toml`.)

VanDelay

📌

@mathspp.com @bitecode.dev according to docs.astral.sh/uv/reference... you should be able to use: uv init --package mycli (i.e. without the --app, because that is the default now)

Oh didn’t know the default. But I never do, so I might just stick to being explicit :p also a bit more future-proof

mathspp.comUsing uv to build and install Python CLI appsThis practical tutorial shows how to use uv to build and install custom Python CLI applications globally on your system.

For a slightly more verbose tutorial with a bit of hand-holding, take a look at this: mathspp.com/blog/using-u...

The reason I added -e is so that changes in the code you make to mycli are immediately visible by your system. If you want to version your CLI properly, I'd omit the `-e` from the installation command. Disclaimer: I'm not a packaging expert. Nor a uv expert.

@bitecode.dev does this look decent / in line with what you've been doing this past year?

Bite Code!

@bitecode.dev

Super nice trick. I've never used it, I just have scripts with inline deps and a uv shebang in a dir added to my PATH. But the advantage of your method is that nobody has to know about the PATH and it works cross platform.

Bite Code!

@bitecode.dev

Mind if I add that to the uv tricks article ?

Tiago Montes

@setnomt.bsky.social