You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
When trying to install airflow following the URL mentioned above I got the following message:
...
ERROR: Cannot install apache-airflow==2.1.0 because these package versions have conflicting dependencies.
The conflict is caused by:
apache-airflow 2.1.0 depends on flask-appbuilder~=3.3
The user requested (constraint) flask-appbuilder==3.1.1
To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict
...
What you expected to happen:
To install flawlessly :)
) were updated on May 12th (PR #15792) but it seems that for some reason the constraints for python-3.9 were not updated accordingly (rest of versions are ok).
How to reproduce it:
On a Linux Box able to run airflow
Create a virtual environment on a server with python==3.9, pip==21.1.2 (previous versions of pip show a different error message)
Thanks for opening your first issue here! Be sure to follow the issue template!
cesaralba
changed the title
Inconsistency between package requirements and constraints: flask-appbuilder
Inconsistency between package requirements and constraints: flask-appbuilder (python 3.9)
Jun 17, 2021
Apache Airflow version: 2.1.0
Kubernetes version (if you are using kubernetes) (use
kubectl version
): N//AEnvironment:
uname -a
): 5.12.10-300.fc34.x86_64What happened:
When trying to install airflow following the URL mentioned above I got the following message:
What you expected to happen:
To install flawlessly :)
** What do you think went wrong?**:
The requirements package for apache-airflow (
airflow/setup.cfg
Line 102 in 6236e7e
How to reproduce it:
On a Linux Box able to run airflow
Anything else we need to know:
I tried to change it in a fork but I wasn't able.
To get the fix done (on bash)
After the change, an installation with a local constraints file worked ok.
The text was updated successfully, but these errors were encountered: