Re: [I] Clean `airflow.utils` and move DAG definition items to Task SDK [airflow]
amoghrajesh commented on issue #51671: URL: https://github.com/apache/airflow/issues/51671#issuecomment-3889198060 The remaining items have been moved to a new epic: https://github.com/apache/airflow/issues/61803 which will be handled after 3.2, closing this one now -- 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]
Re: [I] Clean `airflow.utils` and move DAG definition items to Task SDK [airflow]
amoghrajesh closed issue #51671: Clean `airflow.utils` and move DAG definition items to Task SDK URL: https://github.com/apache/airflow/issues/51671 -- 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]
Re: [I] Clean `airflow.utils` and move DAG definition items to Task SDK [airflow]
amoghrajesh commented on issue #51671: URL: https://github.com/apache/airflow/issues/51671#issuecomment-3844937182 The two pending items are related to dag.test here -- 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]
Re: [I] Clean `airflow.utils` and move DAG definition items to Task SDK [airflow]
KoviAnusha commented on issue #51671: URL: https://github.com/apache/airflow/issues/51671#issuecomment-3430683782 As you all are making these changes, is it already documented somewhere? or shall I work on documentation? -- 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]
Re: [I] Clean `airflow.utils` and move DAG definition items to Task SDK [airflow]
sunank200 commented on issue #51671: URL: https://github.com/apache/airflow/issues/51671#issuecomment-3089206125 For 3.1, the goal is not to strictly remove `airflow.utils` but the goal is to remove imports of sdk from core. -- 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]
Re: [I] Clean `airflow.utils` and move DAG definition items to Task SDK [airflow]
kaxil commented on issue #51671: URL: https://github.com/apache/airflow/issues/51671#issuecomment-2970113529 Yeah, I think so, but I think we can have one in `airflow/utils/__init__.py` similar to https://github.com/apache/airflow/blob/main/airflow-core/src/airflow/operators/__init__.py -- 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]
Re: [I] Clean `airflow.utils` and move DAG definition items to Task SDK [airflow]
uranusjr commented on issue #51671: URL: https://github.com/apache/airflow/issues/51671#issuecomment-2969890045 Do we need to maintain backward compatibility and keep shims in the module? -- 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]
