Skip to content

Commit

Permalink
Proper constraints used for editable builds
Browse files Browse the repository at this point in the history
The constraints specified for editable build were wrong - editable
builds alswayS use "source-providers" constraints.

Fixes: apache#37560.
  • Loading branch information
potiuk committed Feb 20, 2024
1 parent 004dcb7 commit 235b2a9
Showing 1 changed file with 9 additions and 1 deletion.
10 changes: 9 additions & 1 deletion contributing-docs/07_local_virtualenv.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 235b2a9

Please sign in to comment.