Oh, no shebang update until astral-sh/ruff#13021, I'll revert those.

Let's wait for #13597 (comment) to be resolved before merging this. (Edit: resolved now)

I still don't like this. If someone wants to contribute a small fix to typeshed, e.g. stubs for a simple library, they shouldn't be thrown on a tangent about a tool named uv that they don't really even need to use.

python vs python3

I think it is safe to assume that anyone contributing to typeshed already knows how to run Python on their own system. Figuring out whether to put 3 in the command or not is much easier than learning about uv, even if uv is very simple and easy to use.

I still don't like this. If someone wants to contribute a small fix to typeshed, e.g. stubs for a simple library, they shouldn't be thrown on a tangent about a tool named uv that they don't really even need to use.

Yeah my comment at #13597 (comment) will apply here as well

Using it in doc was less about install speed, and more about not having to worry about virtual environments, and whether it exists / is activated.

I could see being told to run a custom tool (uv) when you may not even know that it was part of the installed requirements to be jarring.

I'll update this PR

python vs python3 and .venv vs .venv3 in doc: I guess more of an annoyance where it'd be nice if we were consistant.

This PR is now only scoped to allowing using uv run without having to run --no-project every time.

You may have reasons to not want to modify the pyproject.toml. In which case please voice them! (even if it's just "let's wait for uv to support this"). Since I'm fine with such a change.
But please upvote astral-sh/uv#8666 in that case