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 feb4f40db0 Replace blockquote + Note: with RST note in docs (#29709)
feb4f40db0 is described below
commit feb4f40db0170e0711234076adf45753d65aed2f
Author: Vladimir Mikhaylov <[email protected]>
AuthorDate: Thu Feb 23 11:21:54 2023 +0000
Replace blockquote + Note: with RST note in docs (#29709)
---
docs/apache-airflow/authoring-and-scheduling/serializers.rst | 4 ++--
docs/apache-airflow/core-concepts/taskflow.rst | 4 ++--
docs/apache-airflow/core-concepts/xcoms.rst | 4 ++--
3 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/docs/apache-airflow/authoring-and-scheduling/serializers.rst
b/docs/apache-airflow/authoring-and-scheduling/serializers.rst
index 1413bc3153..7c3315d13a 100644
--- a/docs/apache-airflow/authoring-and-scheduling/serializers.rst
+++ b/docs/apache-airflow/authoring-and-scheduling/serializers.rst
@@ -47,9 +47,9 @@ but its keys need to be of primitive form. In case you are
implementing a regist
not to have circular imports. Typically, this can be avoided by using ``str``
for populating the list of serializers.
Like so: ``serializers = ["my.company.Foo"]`` instead of ``serializers =
[Foo]``.
-::
+.. note::
- Note: Serialization and deserialization is dependent on speed. Use built-in
functions like ``dict`` as much as you can and stay away from using classes and
other complex structures.
+ Serialization and deserialization is dependent on speed. Use built-in
functions like ``dict`` as much as you can and stay away from using classes and
other complex structures.
Airflow Object
--------------
diff --git a/docs/apache-airflow/core-concepts/taskflow.rst
b/docs/apache-airflow/core-concepts/taskflow.rst
index 6f46cdb4cd..8dcd52acd1 100644
--- a/docs/apache-airflow/core-concepts/taskflow.rst
+++ b/docs/apache-airflow/core-concepts/taskflow.rst
@@ -179,9 +179,9 @@ It is good practice to version the objects that will be
used in serialization. T
so that a version 2 is able to deserialize a version 1. In case you need
custom logic
for deserialization ensure that ``deserialize(data: dict, version: int)`` is
specified.
-::
+.. note::
- Note: Typing of ``__version__`` is required and needs to be ``ClassVar[int]``
+ Typing of ``__version__`` is required and needs to be ``ClassVar[int]``
Sensors and the TaskFlow API
diff --git a/docs/apache-airflow/core-concepts/xcoms.rst
b/docs/apache-airflow/core-concepts/xcoms.rst
index 3a6dedea28..8cc3ebaf4b 100644
--- a/docs/apache-airflow/core-concepts/xcoms.rst
+++ b/docs/apache-airflow/core-concepts/xcoms.rst
@@ -38,9 +38,9 @@ You can also use XComs in :ref:`templates
<concepts:jinja-templating>`::
XComs are a relative of :doc:`variables`, with the main difference being that
XComs are per-task-instance and designed for communication within a DAG run,
while Variables are global and designed for overall configuration and value
sharing.
-::
+.. note::
- Note: If the first task run is not succeeded then on every retry task XComs
will be cleared to make the task run idempotent.
+ If the first task run is not succeeded then on every retry task XComs will
be cleared to make the task run idempotent.
Custom XCom Backends
--------------------
