Zanie Blue

I don't think they should always clean the virtual environment. I think it's too common for people to manually manage packages in Python and without an explicit sync it seems...

I think we made a decision on this — we have a toggle now.

Thanks for sharing! > The first issue is that when you run the container you need to activate the virtual env every time You could add the virtual environment's `bin`...

I think both approaches are totally reasonable. We see a "add venv to path" approach more often when you don't have write access to the system.

I'm adding some documentation based on this discussion #4433

We could also frame this differently, like.. ``` toolchain-discovery = prefer-system | prefer-managed | only-system | only-managed ```

What's the difference between `uv-only` and `managed-only` there? I don't think we'll support discovery of Python interpreters in _other_ tool's installation directories. It seems more reasonable to just expect them...

A "system" Python here is any Python toolchain installed on the system i.e. not being managed by uv. Brew Python will come up if it's on the PATH, but we...

This issue is actually completed: https://docs.astral.sh/uv/reference/settings/#python-preference Feel free to open a new one to track support for other managed Python distribution kinds, but we're pretty unlikely to support more.

Nice, I like the look of that