On 11/4/2023 4:57 AM, Jarek Potiuk wrote: > If you want to make sure released Airflow installs in a reproducible > way from the scratch - now and in the future, the only way to achieve > that is described here: > > https://airflow.apache.org/docs/apache-airflow/stable/installation/installing-from-pypi.html > > It involves using constraints. It only works with `pip`. There are > no other ways and other tools that can be achieved easily, so we > strongly recommend you use `pip` when installing Airflow. > > Example installation command for airflow with celery extra and > Python version 3.8 is here: > > pip install "apache-airflow[celery]==2.7.2" --constraint " > https://raw.githubusercontent.com/apache/airflow/constraints-2.7.2/constraints-3.8.txt
Thanks for this reminder and tutorial. When upgrading an Airflow instance installed with virtualenv, should users interact with constraints files the same way? Here's the sequence I'm imagining, per the upgrade docs[1], if I were trying to upgrade to the latest version with Python 3.9 (venv) $ pip install --upgrade apache-airflow==2.7.3 \ > --constraint "https://raw.githubusercontent.com/apache/airflow/constraints-2.7.3/constraints-3.9.txt"; (venv) $ airflow db migrate Is that the right sequence? Is there anything else that should be kept in mind? - Ben [1]: https://airflow.apache.org/docs/apache-airflow/stable/installation/upgrading.html --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@airflow.apache.org For additional commands, e-mail: users-h...@airflow.apache.org
