Don't explicitly install Python. Use uv sync instead of uv add.

[tdhopper]

Thanks for writing up the uv instructions. Here are some tweaks on using uv idiomatically.

[rasbt]

Thanks for the PR! Question: Doesn't uv sync remove packages that are not explicitely defined as dependencies in the pyproject.toml though? Sure, in some cases that's maybe what you want, but I can also see where this is annoying if you

1. setup up your new venv, install a bunch of packages
2. then run uv sync on the pyrpoject.toml and discover those are then gone?

[tdhopper]

That's correct.

My read of this instructions was that they're for setting up the project environment for the first time (it doesn't, for example, include instructions on setting up a venv).

If you want to prevent that, you can do uv sync --inexact.

But beyond that, if you're using pyproject.toml to management dependencies, it's an antipattern to add dependencies to the environment that you're not tracking in the pyproject.toml. uv add and uv pip install shouldn't be used together.

One last point, uv sync is going to explicitly tell you if it installs packages, so it should at least be clear to end users what is going on.

[rasbt]

My read of this instructions was that they're for setting up the project environment for the first time (it doesn't, for example, include instructions on setting up a venv).

That's fair, and I like your changes overall. Thanks for taking the time to do this PR!