ranamit112 opened a new issue #13045: URL: https://github.com/apache/airflow/issues/13045
**Apache Airflow version**: 1.10.7 **Kubernetes version (if you are using kubernetes)** (use `kubectl version`): N.A. **Environment**: - **Cloud provider or hardware configuration**: N.A. - **OS** (e.g. from /etc/os-release): Red Hat Enterprise Linux Server 7.6 (Maipo) - **Kernel** (e.g. `uname -a`): 3.10.0-957.35.2.el7.x86_64 - **Install tools**: pip, python3.7 - **Others**: **What happened**: Could not install airflow 1.10.7 using constraint file for 1.10.7. ``` ERROR: Could not find a version that satisfies the requirement future<0.17,>=0.16.0 (from apache-airflow[celery,postgres,statsd]) ERROR: No matching distribution found for future<0.17,>=0.16.0 ``` **What you expected to happen**: pip install success <!-- What do you think went wrong? --> The 1.10.7 [constraint file](https://github.com/apache/airflow/blob/constraints-1.10.7/constraints-3.7.txt) (that was created using 1.10.10 dependencies) includes a constraint for `future==0.18.2` while the [setup.py](https://github.com/apache/airflow/blob/1.10.7/setup.py#L467) for that version includes the requirement that `future>=0.16.0, <0.17`, which is incompatible. This can be considered part of https://github.com/apache/airflow/issues/12838, as this happens only when using the new pip 20.3 resolver, but I think pip is behaving correctly, and the real problem is in the constraint file. **How to reproduce it**: ``` python3.7 -m venv venv_python37_airflow cd venv_python37_airflow . ./bin/activate python3.7 -m pip install --upgrade pip python3.7 -m pip install wheel AIRFLOW_VERSION=1.10.7 PYTHON_VERSION="$(python --version | cut -d " " -f 2 | cut -d "." -f 1-2)" CONSTRAINT_URL="https://raw.githubusercontent.com/apache/airflow/constraints-${AIRFLOW_VERSION}/constraints-${PYTHON_VERSION}.txt"; python -m pip install "apache-airflow[celery,postgres,statsd]==${AIRFLOW_VERSION}" --constraint ${CONSTRAINT_URL} ``` **Anything else we need to know**: From my testing removing the constraint for `future==0.18.2` solved this meaning it's the only non-valid constraint for this version. I believe this happens in other earlier versions, but I did not test version earlier than 1.10.7. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
