From 516c27b13aa91695aaa30ea1f0ea6701bda6f006 Mon Sep 17 00:00:00 2001 From: Kaxil Naik Date: Tue, 29 Mar 2022 22:15:28 +0100 Subject: [PATCH] Doc: Update description for executor-bound dependencies (#22601) These suggestions were missed in https://github.com/apache/airflow/pull/22573 - https://github.com/apache/airflow/pull/22573/files#r837754616 - https://github.com/apache/airflow/pull/22573/files#r837755144 - https://github.com/apache/airflow/pull/22573/files#r837755355 GitOrigin-RevId: b0b69f3ea7186e76a04b733022b437b57a087a2e --- setup.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/setup.py b/setup.py index b72021d61db..7935b7663a7 100644 --- a/setup.py +++ b/setup.py @@ -1055,12 +1055,12 @@ def replace_extra_requirement_with_provider_packages(extra: str, providers: List In the constraint mechanism we save both - provider versions and it's dependencies version, which means that installation using constraints is repeatable. - For K8s, Celery which are both "Core executors" and "Providers" we have to - add the base dependencies to the core as well - in order to mitigate problems where + For K8s and Celery which are both "Core executors" and "Providers" we have to + add the base dependencies to core as well, in order to mitigate problems where newer version of provider will have less strict limits. This should be done for both extras and their deprecated aliases. This is not a full protection however, the way extras work, this will not add "hard" limits for Airflow and the user who does not use - constraints + constraints. :param extra: Name of the extra to add providers to :param providers: list of provider ids