My opinion is I would rather not preinstall Dask provider because as already mentioned in this thread, this is not technically a breaking change. Users using Dask provider will be able to find out quite easily that their environment is not working without Dask dependency. To me it makes more sense to not have it preinstalled by default and only if needed, users just need to add it to their dependencies.
I also feel like (I might be wrong) this decision might take precedence on all the future similar decisions (whether provider X should be preinstalled by default in Airflow after having moved out the code from core to providers) and I feel, on the long term, the general "good" approach is to let users install the dependencies/providers they want without preinstalling them. I am not saying this is true for all providers, the ones that are essential to Airflow should, of course, be preinstalled. But this is not the case with Dask I think. On 2023-07-20, 3:59 PM, "Daniel Standish" <daniel.stand...@astronomer.io.inva <mailto:daniel.stand...@astronomer.io.inva>LID> wrote: CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. > I guess the question is not "can we do it" but more "should we do it" :D right :) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org For additional commands, e-mail: dev-h...@airflow.apache.org
