amoghrajesh commented on code in PR #58479: URL: https://github.com/apache/airflow/pull/58479#discussion_r2541924193
########## airflow-core/docs/core-concepts/taskflow.rst: ########## @@ -201,6 +201,33 @@ Sensors and the TaskFlow API For an example of writing a Sensor using the TaskFlow API, see :ref:`Using the TaskFlow API with Sensor operators <taskflow-using-sensors>`. +Decorator Utilities Migration +----------------------------- + +Several helper functions previously located in ``airflow.utils.decorators`` have been moved to more appropriate modules. + +The following imports are deprecated and will be removed in a future version: + +.. code-block:: python + + from airflow.utils.decorators import classproperty + from airflow.utils.decorators import remove_task_decorator + from airflow.utils.decorators import fixup_decorator_warning_stack + +Use the updated import paths instead: + +.. code-block:: python + + # classproperty is now part of the deadline model + from airflow.models.deadline import classproperty + + # decorator utilities relocated to the Task SDK internal definitions module + from airflow.sdk.definitions._internal.decorators import remove_task_decorator Review Comment: No its not fine to write about internal modules thats why those are in `_internal` -- which means that they are not used anywhere in the codebase apart from within task sdk and aren't part of the public dag authoring interface of Airflow. Everyting of decorators that needs to be exposed is here: https://github.com/apache/airflow/blob/main/task-sdk/src/airflow/sdk/bases/decorator.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]
