potiuk commented on issue #51545: URL: https://github.com/apache/airflow/issues/51545#issuecomment-2980189475
> A tight coupling between task-sdk and any "server side" component is the opposite to one of the goals of AIP-72 (I'm not sure we ever explicitly said this, but the first point of motivation for the AIP says "Dependency conflicts for administrators supporting data teams using different versions of providers, libraries, or python packages") I thin we agree here for task-sdk. My comment was only for `non-task-sdk` packages (i.e. all packages resulting from splitting airflow-core). As explained above - `task sdk` should be fully standalone and should have duplication if needed and should be independently versioned - I wrote it above. And providers should depend exclusively on task-sdk. Task SDK should have everything needed to run any kind of worker and should not depend on any parts of airflow-core including "airflow-common-utils". But all the rest of packages (core, common-util, api-server if we have it etc.) should be all pinned with the same version - i.e. tested and released together. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
