> > *For Problem (1)* there is an easy workaround to use pip with legacy > resolver or pip <= 20.3.3 that allows installing new dependencies even with > conflicts for the provider. We also have notes everywhere on our > installation guide ( > https://airflow.apache.org/docs/apache-airflow/stable/installation.html#installation-tools) > that says: > > There was a recent (November 2020) change in resolver, so currently only >> 20.2.4 version is officially supported, although you might have a success >> with 20.3.3+ version (to be confirmed if all initial issues from pip 20.3.0 >> release have been fixed in 20.3.3). In order to install Airflow you need to >> either downgrade pip to version 20.2.4 pip install --upgrade pip==20.2.4 or, >> in case you use Pip 20.3, you need to add option --use-deprecated >> legacy-resolver to your pip install command. > > > But we should fix it in master with *solution (1)* so when we release > Airflow 2.0.2 (a month or so from now) we don't have such an issue and > don't need a workaround. >
Yep. It is not fatal. PIP 20.2.4 is still the only officially supported and the documentation is very clear about it. So yeah - we do not Have to release it now. We can also update the documentation slightly to make it clear that having those PIP warnings for google provider is not a problem in the first installation case. and explain it. Currently the only problem is google 2.0 provider. > > *For Problem (2) *We should include the providers in constraints file > (example add *apache-airflow-provider-google==1.0.0*) and once a > constraints file is published we should not change it. Otherwise, it > defeats the purpose of "repeatable installation". I would be against that > change. We should not change the constraints tag (e.g constraints-2.0.0) > once 2.0.0 is released with it and treat it same as 2.0.0 tag. > Yep. Good idea. That might be a better solution. Agree it would solve the problem as well. We can even retro-actively do it now and make 2.0.1 installation point to older versions of the google provider to avoid the warnings from point 1 altogether until 2.0.1 is released/ > > +48 660 796 129
