Add uv among command example to work with virtual env and quarto

[cderv]

Thanks, the suggestion to wrap quarto render inside uv run works here and seems like the cleanest option.

You can also leverage uv run directly, as the command will be ran in the virtual env

Maybe content about uv could be added to the Quarto docs on virtual environments?

https://quarto.org/docs/projects/virtual-environments.html

Originally posted by @westat-schneider in #12053

We are mentionning venv and how to create it. uv seems widely use and it could be interesting to document it too.

[mcanouil]

FWIW, I agree with the addition of uv example, but I am a bit concerned that it will need updates/maintenance if we add it now or in few months, as the API evolves quite rapidly and with breaking changes.

[cderv]

The only thing we really need from uv in my opinion is

• Explain that it can be used with Quarto
• Link to their doc one how to create virtualenv with it

then mention

• Activating the venv (which is not a uv command), then quarto render - this is what we document already
• Run uv run quarto render

I was not planning to go deeper in uv api and so was not really concerned about API change on their part.

What do you think could be worth waiting for more stability ?

[mcanouil]

If uv run is stable in the sense that the command itself is not going to change or its behaviour, it's fine.

I did not check uv run but I've seen few days ago in the changelog:

uv publish is no longer in preview

I'm just saying to check the status.

[cderv]

ok - good to keep in mind. I was wondering if you spotted anything specific. 👍

[kodonian]

I’m trying to use virtual Python environments created with uv for my Quarto projects to ensure reproducibility and isolated dependencies. Activating the environment works in the current terminal session, but as soon as I reopen a terminal for package installation the activation is lost.

I’ve seen earlier discussions around Python kernel selection and the QUARTO_PYTHON environment variable (e.g. #12506, #11804), but none seem to provide a seamless solution across multiple Quarto projects.

Since I’m working with several Quarto projects in parallel, each using its own .venv, I’d like a project-local way to configure which Python environment should be used — ideally without requiring global kernel installation or modifying shared paths.

I tried globally unsetting QUARTO_PROJECT and using a local _environment file to set QUARTO_PYTHON per project, but that doesn’t seem to be interpreted at all. Kernel configuration via ipykernel works, but introduces overhead and breaks portability due to hardcoded paths.

Is there currently a way to specify the Python environment path (e.g. .venv/bin/python) in _quarto.yml?
If not, would this be a suitable candidate for a feature request?

[mcanouil]

@kodonian could you open a new GitHub discussion (not an issue)? This thread is not the place for your question or to discuss something that is not about adding examples for uv.

[kodonian]

Found a related discussion entry #11257 and added my observations to the discussion there.