potiuk commented on issue #27292: URL: https://github.com/apache/airflow/issues/27292#issuecomment-1550157300
> @potiuk Given [#30067 (comment)](https://github.com/apache/airflow/pull/30067#issuecomment-1549960088) I was curious if there has been any additional conversations around extras vs provider breakout. (I have a small preference towards extras since it seems easier / faster to implement given the conversations above). No - no discussions. And I think they are not needed. I **personally** think once we get it updated now and keep on updating to the new versions (which should happen pretty much automatically as soon as we remove pretty much all the upper-binding dependencies) the problem will all but disappear. Vast majority of the problem came from the fact that we were half before and half after a huge backwards incompatible change introduced accross all google python libraries some 4 years ago. The #30067 puts that dychotomy to an end. I am actually going to actively chase and remove all the upper-bind limitations that we have elsewhere, becuase this is IMHO the only way we can long term keep sanity. We already have in place the system that checks if there are no breaking changes in deps released in main and for a long time we are faster to detect and fix them than anyone else (see for example this issue from today where our canary builds detected and we fixed alembic incompatibility before the first user reported it to us: -- 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]
