Zanie Blue

I think we'd implement our own build backend before embedding a Python one into uv itself. Related: - https://github.com/astral-sh/uv/issues/6299

It's a cool idea though. The offline use-case for #3957 is interesting.

At the bottom, we suggest `uv run help` to see the long-form help.

Sorry, `uv help run` — `uv help` is the interface for the CLI reference.

We had a relatively comprehensive way of doing this before: https://github.com/astral-sh/uv/blob/e0ac5b4e84d2544c915b83bfb50776b468cdb38d/crates/platform-host/src/linux.rs I'm not sure there are problems with it — mostly I think the plan was to make it simpler...

The comment at https://github.com/astral-sh/uv/pull/4160#issuecomment-2157850192 provides important context on the current state of things. It was removed in https://github.com/astral-sh/uv/pull/2381 when we moved to relying on Python's platform detection — we of...

Basically, we should totally add support back and we can probably mostly copy the old implementation from the `platform-host` crate. However, there are significant problems with using python-build-standalone on Alpine...

So there's two parts 1. Restoring our previous musl detection code: [source](https://github.com/astral-sh/uv/blob/e0ac5b4e84d2544c915b83bfb50776b468cdb38d/crates/platform-host/src/linux.rs) 2. Improving python-build-standalone on Alpine: e.g. fixing https://github.com/astral-sh/uv/pull/2382 For (1) we'll probably want to simplify the code some,...

@konstin could give far more context on (2)

Yeah if the current ones (libc) can't be used at all, I think it's an important improvement to download the correct musl distribution. > Hmm not sure we need all...