You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "prakharcode (via GitHub)" <gi...@apache.org> on 2026/04/02 19:49:10 UTC
Re: [I] Proposal: UvOperator – A lightweight, decoupled provider for UV environments [airflow]
prakharcode commented on issue #60621:
URL: https://github.com/apache/airflow/issues/60621#issuecomment-4180121825
I checked the source for Venv operator, and it does take care of using UV by checking the config and then the environment for UV, then constructs the venv using UV (if selected) [ref1](https://github.com/apache/airflow/blob/5497cd16be220a5e5b9ad1ed571de22cca261e95/providers/standard/src/airflow/providers/standard/utils/python_virtualenv.py#L45) [ref2](https://github.com/apache/airflow/blob/5497cd16be220a5e5b9ad1ed571de22cca261e95/providers/standard/src/airflow/providers/standard/utils/python_virtualenv.py#L85).
I think there is an advantage to having a `UVtoolOperator` to execute some of cli tools as an alternative to install the tool in the environment. Esp useful for cases like dbt.
This can be a light wrapper over the existing BashOperator but would provide specific flags (`--from`, `--with`, `--python`). Let me know if this makes sense or we expect users to use BashOperator only and not provide specific uv based operaotors.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org