From 235b2a9423da3ff0dc42671f115bd2d73e2527fb Mon Sep 17 00:00:00 2001 From: Jarek Potiuk Date: Tue, 20 Feb 2024 22:29:24 +0100 Subject: [PATCH] Proper constraints used for editable builds The constraints specified for editable build were wrong - editable builds alswayS use "source-providers" constraints. Fixes: #37560. --- contributing-docs/07_local_virtualenv.rst | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/contributing-docs/07_local_virtualenv.rst b/contributing-docs/07_local_virtualenv.rst index 54468dbec6404..29cdea767c680 100644 --- a/contributing-docs/07_local_virtualenv.rst +++ b/contributing-docs/07_local_virtualenv.rst @@ -367,7 +367,15 @@ all basic devel requirements and requirements of google provider as last success .. code:: bash pip install -e ".[devel,google]"" \ - --constraint "https://raw.githubusercontent.com/apache/airflow/constraints-main/constraints-3.8.txt" + --constraint "https://raw.githubusercontent.com/apache/airflow/constraints-main/constraints-source-providers-3.8.txt" + +Make sure to use latest main for such installation, those constraints are "development constraints" and they +are refreshed several times a day to make sure they are up to date with the latest changes in the main branch. + +Note that this might not always work as expected, because the constraints are not always updated +immediately after the dependencies are updated, sometimes there is a very recent change (few hours, rarely more +than a day) which still runs in ``canary`` build and constraints will not be updated until the canary build +succeeds. Usually what works in this case is running your install command without constraints. You can upgrade just airflow, without paying attention to provider's dependencies by using the 'constraints-no-providers' constraint files. This allows you to keep installed provider dependencies