@lwjohnst86 Just one comment on this. I agree that whether we use uvx quarto or just quarto doesn't matter, but when I originally added some of these tools in #173 I intentionally used uv run quarto so that quarto used the Python version in .venv/bin/python (same as setting QUARTO_PYTHON=.venv/bin/python quarto).
It seems like this was changed to uvx in #255 and I just want to double check that we intentionally want to make this change to the Python path that quarto sees. Since python is not used as often in the data package templates as in the python package templates, this is probably not a large issue, but it still seems more desirable that any python code that is potentially used in the websites are executed using the Python version managed by uv in the project directory rather than system Python.
Originally posted by @joelostblom in #263 (comment)
@lwjohnst86 Just one comment on this. I agree that whether we use
uvx quartoor justquartodoesn't matter, but when I originally added some of these tools in #173 I intentionally useduv run quartoso that quarto used the Python version in.venv/bin/python(same as settingQUARTO_PYTHON=.venv/bin/python quarto).It seems like this was changed to
uvxin #255 and I just want to double check that we intentionally want to make this change to the Python path that quarto sees. Since python is not used as often in the data package templates as in the python package templates, this is probably not a large issue, but it still seems more desirable that any python code that is potentially used in the websites are executed using the Python version managed by uv in the project directory rather than system Python.Originally posted by @joelostblom in #263 (comment)