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 49ded9f533 Update serializers.rst (#40597)
49ded9f533 is described below

commit 49ded9f5330a6edaf88c1572098d94c643ccee77
Author: Federico Caselli <[email protected]>
AuthorDate: Thu Jul 4 15:28:33 2024 +0200

    Update serializers.rst (#40597)
    
    Mention that ``serialize`` cannot return bytes
---
 docs/apache-airflow/authoring-and-scheduling/serializers.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/apache-airflow/authoring-and-scheduling/serializers.rst 
b/docs/apache-airflow/authoring-and-scheduling/serializers.rst
index 5db998efce..ad752de950 100644
--- a/docs/apache-airflow/authoring-and-scheduling/serializers.rst
+++ b/docs/apache-airflow/authoring-and-scheduling/serializers.rst
@@ -42,7 +42,7 @@ It does not need to serialize the values in the dict, that 
will be taken care of
 form.
 
 Objects that are not under control of Airflow, e.g. ``numpy.int16`` will need 
a registered serializer and deserializer.
-Versioning is required. Primitives can be returned as can dicts. Again 
``dict`` values do not need to be serialized,
+Versioning is required. Primitives, excluding ``bytes``, can be returned as 
can dicts. Again ``dict`` values do not need to be serialized,
 but its keys need to be of primitive form. In case you are implementing a 
registered serializer, take special care
 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]``.

Reply via email to