kacpermuda commented on PR #41637: URL: https://github.com/apache/airflow/pull/41637#issuecomment-2301967318
> The common.compat provider is already there. My main concern, though I’m not sure if it’s entirely valid, is that we previously discussed having a `common.utils` provider specifically designed to make it easier to add simple functionality, without external dependencies, to all providers, so that they do not have to rely on core Airflow version. The `common.compat` provider, as I understand, is meant to serve as a “proxy” that ensures code within providers functions without errors, with potentially fewer features, regardless of the Airflow version or other provider versions, but we should gradually remove things from there as we raise min. dependency versions f.e. for Airflow core. So it looks similar, but I'm not quite sure it's the same. Introducing this type of deprecation module into `common.compat` could make it more multi-functional, and it can be beneficial, I'm just not sure if i understand the background logic behind `common.compat` -- 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]
