GitHub user GiorgioRafael added a comment to the discussion: Confused at the mixing of `uv` and `pip`/`venv` instructions in Quick Start guide
The guide is currently mixing two alternative paths. If you choose `uv`, you do not need to run the `pip`/`venv` block, but you do need to create a Python environment before evaluating the line that calls `python -c`. A consistent `uv`-only order is: ```bash # Airflow requires Linux/WSL2 on Windows export AIRFLOW_HOME=~/airflow mkdir -p $AIRFLOW_HOME cd $AIRFLOW_HOME # Install uv using its official installation guide, then: PYTHON_VERSION=3.12 AIRFLOW_VERSION=3.3.0 uv python install $PYTHON_VERSION uv venv --python $PYTHON_VERSION airflow_venv source airflow_venv/bin/activate CONSTRAINT_URL=https://raw.githubusercontent.com/apache/airflow/constraints-${AIRFLOW_VERSION}/constraints-${PYTHON_VERSION}.txt uv pip install apache-airflow==${AIRFLOW_VERSION} --constraint $CONSTRAINT_URL airflow version airflow standalone ``` The `Command 'python' not found` error occurs because installing the `uv` executable alone does not necessarily place an unversioned `python` executable on `PATH`, and the guide evaluates `python -c ...` before showing the missing `uv venv` step. Setting `PYTHON_VERSION` explicitly avoids that circular dependency; after activating `airflow_venv`, `python` will also resolve normally. The current Airflow quick start lists Python 3.10–3.14 as supported: https://airflow.apache.org/docs/apache-airflow/stable/start.html. `uv` can install and manage the interpreter itself: https://docs.astral.sh/uv/guides/install-python/. So your reading is correct: step 2 should show the `uv python`/`uv venv` setup, while the existing `pip`/`venv` block is a separate alternative. GitHub link: https://github.com/apache/airflow/discussions/71000#discussioncomment-17889047 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
