Zanie Blue

Similarly, this does not solve the version stability goals for our managed Python installations as mentioned in https://github.com/astral-sh/uv/pull/8433#issuecomment-2428037536 and as implemented in #8458. As @konstin concludes, I think this is...

I guess an open question for me is if we want to provide a setting for this, i.e., `UV_VENV_PYTHON_LINK = resolve | base | no-resolve` (don't focus on the names...

> Critically, though, it would be actively wrong to use /home/konsti/.local/bin as the virtual environment home. The same is true for the managed Python design, right? That's not a valid...

Yeah all for changing the default. I'm also leaning further towards the idea that we should support configuring the strategy as an escape hatch for workflows this change breaks though;...

> (I'm sort of hesitant to add settings for the strategy without clear demand.) Fair, but we already have some clear cases where we need to resolve the link to...

Hm it's weird that we wouldn't write output when using `subprocess`. I'd consider that a bug, if we can reproduce. @Gankra is considering allowing interaction with current state from a...

Oh.. yeah the progress bars don't work in a non-interactive mode (and I wouldn't expect them to). They require repeated drawing in the terminal. I don't think we'll implement simple...

Still TBD, @Gankra would have more details but we're still designing this. See also https://github.com/astral-sh/uv/issues/411

A couple concerning changes

It'd be great to include `{APP_NAME}_INSTALL_DIR` and `INSTALLER_NO_MODIFY_PATH` in the installer help menu. e.g., it's currently: ``` ❯ curl -LsSf https://astral.sh/uv/install.sh | sh -s -- --help uv-installer.sh The installer for...