Skip to content

Comments

Filter out non-editable apache-airflow from constraints.#25847

Merged
potiuk merged 1 commit intoapache:mainfrom
potiuk:filter-out-non-editable-apache-airflow-from-constraints
Aug 20, 2022
Merged

Filter out non-editable apache-airflow from constraints.#25847
potiuk merged 1 commit intoapache:mainfrom
potiuk:filter-out-non-editable-apache-airflow-from-constraints

Conversation

@potiuk
Copy link
Member

@potiuk potiuk commented Aug 20, 2022

The constraint files should not contain apache-airflow. So far
apache-airflow has been automatically filtered out by the fact that it
has been an editable installation and we filtered out all editable
and file installations from pip freeze.

However as of ~12 August 2022, likely setuptools change triggered
a slight behaviour change when eager-upgrade installation of
providers from PyPi was run in the CI image. Previously airflow
remained an editable install, but as of 12th of August, such an
installation causes removal of editable airlfow install and
reinstalls it in non-editable mode. While this change is somewhat
confusing, we have to protect against it and remove apache-airflow
from pip freeze also in non-editable mode.


^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

The constraint files should not contain apache-airflow. So far
apache-airflow has been automatically filtered out by the fact that it
has been an editable installation and we filtered out all editable
and file installations from `pip freeze`.

However as of ~12 August 2022, likely setuptools change triggered
a slight behaviour change when `eager-upgrade` installation of
providers from PyPi was run in the CI image. Previously airflow
remained an editable install, but as of 12th of August, such an
installation causes removal of editable airlfow install and
reinstalls it in non-editable mode. While this change is somewhat
confusing, we have to protect against it and remove apache-airflow
from `pip freeze` also in non-editable mode.
@potiuk potiuk merged commit cdbad44 into apache:main Aug 20, 2022
@potiuk potiuk deleted the filter-out-non-editable-apache-airflow-from-constraints branch August 20, 2022 11:47
potiuk added a commit that referenced this pull request Aug 20, 2022
The constraint files should not contain apache-airflow. So far
apache-airflow has been automatically filtered out by the fact that it
has been an editable installation and we filtered out all editable
and file installations from `pip freeze`.

However as of ~12 August 2022, likely setuptools change triggered
a slight behaviour change when `eager-upgrade` installation of
providers from PyPi was run in the CI image. Previously airflow
remained an editable install, but as of 12th of August, such an
installation causes removal of editable airlfow install and
reinstalls it in non-editable mode. While this change is somewhat
confusing, we have to protect against it and remove apache-airflow
from `pip freeze` also in non-editable mode.

(cherry picked from commit cdbad44)
@ephraimbuddy ephraimbuddy added this to the Airflow 2.4.0 milestone Sep 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants