GitHub user amoghrajesh edited a discussion: How should we import Task SDK items in core?
Now that we are winding up porting definitions and general items to task sdk that can serve as building blocks for building dags for the DAG author, one thought that pops is -- how do we import "correctly" into the core from task sdk. For more context, "BaseOperatorLink" is a definition users would need to create their OperatorLinks, but not something like lets say "DAG" / "Params". So what would be the right way to import in core? The entire file path (from airflow.sdk.definitions.baseoperatorlink import BaseOperatorLink) or just holistically from "sdk" (from airflow.sdk import BaseOperatorLink). Related discussion https://github.com/apache/airflow/pull/47008#discussion_r1979071671 GitHub link: https://github.com/apache/airflow/discussions/47486 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
