Oh I misunderstood -- I thought you were suggesting putting the
transitive deps of apache-airflow-providers-google v2.0 in to
constraint-2.0 files etc.
Cool
On Thu, 11 Feb, 2021 at 12:11, Jarek Potiuk <[email protected]> wrote:
> This unfortunately means that people would be unable to install v1
of the google provider anymore -- forcing them to upgrade.
Not really. If we specify just this: [google] ->
"apache-airflow-providers-google" - any provider version could be
installed.
On Thu, Feb 11, 2021 at 12:07 PM Ash Berlin-Taylor <[email protected]
<mailto:[email protected]>> wrote:
On Thu, 11 Feb, 2021 at 00:34, Jarek Potiuk <[email protected]
<mailto:[email protected]>> wrote:
*Solution proposal:*
Every time when we release a new wave of providers, we regenerate
the constraints for all past released 2.* versions of airflow, so
that the new providers are taken into account and they can install
cleanly with `pip install apache-airflow[provider]==2.0.N
--constraint == .... 2.0.N/python ...
Both problems can be solved rather easily. 1) requires 2.0.2
release of Airflow, 2) can be implemented any time (happy to do it).
Let me know what you think.
This unfortunately means that people would be unable to install v1
of the google provider anymore -- forcing them to upgrade.
I'm not sure there's a _ready_ solution to this though.
-ash
--
+48 660 796 129
