hterik commented on PR #27264: URL: https://github.com/apache/airflow/pull/27264#issuecomment-1457771312
> > @potiuk what do you mean by unsuable ? ( I've been using airflow with python 3.11 for more than 3 months, I only use the cncf provider ) > > If you have airflow but cannot use google, snowflake, databricks, and few other providers, I'd say it's next to unusable. We also use Airflow with hardly any providers. Just cncf+celery+docker, to orchestrate our business logic in taskflow. It still gives plenty of value in this configuration. Isn't the idea of providers to decouple the core from dependency explosion, exactly to prevent ending up in situation such as this where dependency deep inside a single provider blocks the rest. Maybe this is already possible if one installs airflow manually via pip? Right now I've mostly used the pre-packaged `slim-` docker images, that don't come with any providers installed. Could it be an option to release slim images for 3.11 while waiting for providers to release the full images? Of course having everything compatible and verified to work together is better to avoid variants, what kind of time frame do you think is reasonable before choosing to ignore some optional providers? -- 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]
