Ahh! good one :). On Wed, Dec 2, 2020 at 5:34 AM Philippe Gagnon <philgagn...@gmail.com> wrote:
> There is also an option to force usage of the old dependency resolver: > > --use-deprecated=legacy-resolver > > But hopefully we find a more sustainable solution going forward! > > BR > > Philippe > > On Tue, Dec 1, 2020 at 10:01 AM Jarek Potiuk <jarek.pot...@polidea.com> > wrote: > >> For those who want to install Airflow 1.10.* today and failing. Please >> check your PIP version. >> >> PIP 20.3 was released yesterday (https://pip.pypa.io/en/stable/news/) >> and it contains a new resolver that might break installation for older >> versions of Airflow. >> >> The solution (for now) is to downgrade to 20.2.4 before installing >> Airflow: >> >> pip install --upgrade pip==20.2.4 >> >> Our Dockerfiles (both for 2.0 and upcoming 1.10.14) will have pip pinned >> to 2.20.4 for now: https://github.com/apache/airflow/pull/12738 >> >> I have also managed to get non-conflicting dependencies a few days ago >> for both 2.0 and 1.10 and while I had problems with the new resolver when I >> tested it in the old PIP I will try to make it works. >> >> Hopefully, both 2.0 and the upcoming 1.10.14 will work with the new pip. >> >> Thank you for your understanding! >> >> J. >> >> >> -- >> >> Jarek Potiuk >> Polidea <https://www.polidea.com/> | Principal Software Engineer >> >> M: +48 660 796 129 <+48660796129> >> [image: Polidea] <https://www.polidea.com/> >> >> -- Jarek Potiuk Polidea <https://www.polidea.com/> | Principal Software Engineer M: +48 660 796 129 <+48660796129> [image: Polidea] <https://www.polidea.com/>
