I prefer DAG, since it is what is actually imported.
from airflow.sdk import DAG
my_dag = DAG(
dag_id="my_dag_name",
start_date=datetime.datetime(2021, 1, 1),
schedule="@daily",
)
EmptyOperator(task_id="task", dag=my_dag)
on the other side, there is also dag decorator
from airflow.sdk import dag
@dag(start_date=datetime.datetime(2021, 1, 1), schedule="@daily")
def generate_dag():
EmptyOperator(task_id="task")
It will be nice to pick the preferred way and keep the terminology 1:1.
út 14. 10. 2025 v 21:11 odesílatel Constance Martineau via dev
<[email protected]> napsal:
>
> Hi everyone,
>
> Just to wrap up the dag vs DAG vs Dag nomenclature discussions we've been
> having over the last few months, I would like to formally call a vote to
> standardize on "Dag".
>
> Jens already updated the docs for 3.1 via this PR
> <https://github.com/apache/airflow/pull/55097>, so hopefully this is just a
> formality.
>
> Discussion threads:
>
> - https://lists.apache.org/thread/lktrzqkzrpvc1cyctxz7zxfmc0fwtq2j
> - https://lists.apache.org/thread/5fn1n188f99jspt627qhqsp2pznq545s
>
>
> Thank you to everyone who took part in the conversations. The vote will run
> for ~3 days, and last till Friday October 17, 2025 at 7:30pm (countdown link
> <https://countingdownto.com/?c=6644364>).
>
> Everyone is encouraged to vote, although only PMC members and Committer's
> votes are considered binding.
>
> Please consider this my +1 (non-binding).
> --
>
> Constance
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
