This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new 573d37b408c docs: remove outdated directed acyclic graph description
(#55096)
573d37b408c is described below
commit 573d37b408c694d966a1cbbc466fb1c449a146a7
Author: Wei Lee <[email protected]>
AuthorDate: Sat Aug 30 19:37:01 2025 +0800
docs: remove outdated directed acyclic graph description (#55096)
---
airflow-core/docs/core-concepts/dags.rst | 2 +-
airflow-core/src/airflow/models/dag.py | 2 +-
task-sdk/src/airflow/sdk/definitions/dag.py | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/airflow-core/docs/core-concepts/dags.rst
b/airflow-core/docs/core-concepts/dags.rst
index 2c520cd1dba..f2010bc558e 100644
--- a/airflow-core/docs/core-concepts/dags.rst
+++ b/airflow-core/docs/core-concepts/dags.rst
@@ -101,7 +101,7 @@ Dags are nothing without :doc:`tasks` to run, and those
will usually come in the
Task Dependencies
~~~~~~~~~~~~~~~~~
-A Task/Operator does not usually live alone; it has dependencies on other
tasks (those *upstream* of it), and other tasks depend on it (those
*downstream* of it). Declaring these dependencies between tasks is what makes
up the Dag structure (the *edges* of the *directed acyclic graph*).
+A Task/Operator does not usually live alone; it has dependencies on other
tasks (those *upstream* of it), and other tasks depend on it (those
*downstream* of it). Declaring these dependencies between tasks is what makes
up the Dag structure.
There are two main ways to declare individual task dependencies. The
recommended one is to use the ``>>`` and ``<<`` operators::
diff --git a/airflow-core/src/airflow/models/dag.py
b/airflow-core/src/airflow/models/dag.py
index fad01299377..9d801c197e6 100644
--- a/airflow-core/src/airflow/models/dag.py
+++ b/airflow-core/src/airflow/models/dag.py
@@ -302,7 +302,7 @@ def _convert_max_consecutive_failed_dag_runs(val: int) ->
int:
@attrs.define(hash=False, repr=False, eq=False, slots=False)
class DAG(TaskSDKDag, LoggingMixin):
"""
- A dag (directed acyclic graph) is a collection of tasks with directional
dependencies.
+ A dag is a collection of tasks with directional dependencies.
A dag also has a schedule, a start date and an end date (optional). For
each schedule,
(say daily or hourly), the DAG needs to run each individual tasks as their
dependencies
diff --git a/task-sdk/src/airflow/sdk/definitions/dag.py
b/task-sdk/src/airflow/sdk/definitions/dag.py
index 086207c8e2f..2c8fe8518fb 100644
--- a/task-sdk/src/airflow/sdk/definitions/dag.py
+++ b/task-sdk/src/airflow/sdk/definitions/dag.py
@@ -250,7 +250,7 @@ def _default_task_group(instance: DAG) -> TaskGroup:
@attrs.define(repr=False, field_transformer=_all_after_dag_id_to_kw_only,
slots=False)
class DAG:
"""
- A dag (directed acyclic graph) is a collection of tasks with directional
dependencies.
+ A dag is a collection of tasks with directional dependencies.
A dag also has a schedule, a start date and an end date (optional). For
each schedule,
(say daily or hourly), the DAG needs to run each individual tasks as their
dependencies
