ags 0.3.2

annotation guided serialization

AGS: Annotation Guided Serialization

The ags module facilitates the serialization and deserialization of arbitrary Python objects to a supported backend format, currently JSON, YAML, and the home grown UCSL. It does so by recursively converting the objects to the domain of the backend -- primitive types such as integers, strings and lists -- before passing them on for serialization. Conversely, after deserialization the primitive types are converted back from primitive types to the actual objects.

The approach that AGS takes is different from a project such as jsonpickle, which employs a bijective map from the space of arbitrary Python objects to the JSON domain. AGS in contrast applies a simpler, non-bijective map, aimed at cleaner files that are suitable for manual editing, at the expense of reversibility.

To restore reversibility, additional information is provided to the serialize and deserialize operations in the form of type annotations. The thinking here is that many modern codes already have type annotations in place, so this information is readily available. For codes that at present lack type annotations, it is a motivation to go with the times and migrate to static typing.

Here is a simple example of AGS in use, featuring some data types that would ordinarily trip up a JSON or YAML engine:

>>> import dataclasses, enum, ags
>>>
>>> @dataclasses.dataclass
... class Point:
...     value: complex
...     end: float|None = None
>>>
>>> class Axis(enum.Enum):
...     real = 1
...     imag = 2
>>>
>>> L = list[Point|Axis]
>>> items: L = [Point(1+2j), Axis.real, Point(1j,1.5)]
>>>
>>> ags.dump("data.yml", items, L)
>>> ags.load("data.yml", L) == items
True

The dump and load function are passed L, as the items object does not carry its own annotation. From here on the annotations of the type object are used to guide the recursive map, resulting in a cast of both the union and dataclasses to dictionaries. The generated data.yml file is:

- Point:
    value: 1+2j
    end: null
- Axis: real
- Point:
    value: 1j
    end: 1.5

The desired serialization backend is based on the file extension: .json for json and .yml for yaml. Alternatively there are dump and load functions in the relevant submodules (ags.json and ags.yaml) that take a file-like argument instead. These modules also provide dumps and loads functions for serialization to/from a string.

Serialization backends

AGS currently supports three serialization backends: JSON, YAML and UCSL. Here we specify how these backends handle type annotations str, int, float, complex, bool, datetime.date, datetime.time, datetime.datetime, list[T], tuple[T, ...], tuple[T1, T2, T3], dict[K, V], typing.Optional[T] or T|None, and typing.Union[T1, T2, T3] or T1|T2|T3:

JSON

The JavaScript Object Notation file format defines the primitives number, string, boolean, array of primitives, a mapping from a string to a primitive, and null.

• str, int, float, bool

  Passed through.

• complex

  Complex numbers without an imaginary part are converted to a float, the rest to a string in Python notation (e.g. 1+2j).

• bytes

  Bytes are converted to a base85 encoded string. Alternatively, if the bytes sequence matches an encoded unicode string, then this string prefixed with the encoding and a colon (like utf8:) is also valid (the colon is excluded from the base85 character set).

• datetime.date, datetime.time, datetime.datetime

  Date objects are converted to a string in ISO 8601 format.

• list[T], tuple[T, ...], tuple[T1, T2, T3]

  Lists and tuples are converted to lists of their converted items. Item type annotations (e.g. list[int]) are required. Both uniform tuples (tuple[int, ...]) and fixed length tuples (tuple[int, str]) are supported.

• dict[K, V]

  Dictionaries are converted to dictionaries with their keys and values converted. Annotations for both key and value are mandatory.

• typing.Optional[T] or T|None

  Optional values are converted according to the above rules for T or set to null if left undefined.

• typing.Union[T1, T2, T3] or T1|T2|T3

  Unions of multiple types are converted to a single item dictionary, where the key is the name of the type and the value the object.

YAML

The YAML Ain’t Markup Language is a superset of JSON as of version 1.2, which means a JSON file is valid YAML, but every any YAML file is valid JSON. YAML notably adds the date and binary primitives, which AGS supports by passing them unchanged. Other Python objects are converted identically to the JSON backend:

• str, int, float, bool, bytes, datetime.date, datetime.time, datetime.datetime

  Passed through.

• complex

  Complex numbers without an imaginary part are converted to a float, the rest to a string in Python notation (e.g. 1+2j).

• list[T], tuple[T, ...], tuple[T1, T2, T3]

  Lists and tuples are converted to lists of their converted items. Item type annotations (e.g. list[int]) are required. Both uniform tuples (tuple[int, ...]) and fixed length tuples (tuple[int, str]) are supported.

• dict[K, V]

  Dictionaries are converted to dictionaries with their keys and values converted. Annotations for both key and value are mandatory.

• typing.Optional or T|None

  Optional values are converted according to the above rules or set to null if left undefined.

• typing.Union or T1|T2|T3

  Unions of multiple types are converted to a single item dictionary, where the key is the name of the type and the value the object.

UCSL

The Ultra Compact Serialisation Language is a custom language specifically designed for the AGS concept. This is an evolution of the stringly project, which used a different notation but otherwise similar concepts. It's primary use case is command line arguments and environment variables.

UCSL has only the string primitive, and relies entirely on type annotations for interpretation. This means the string 123 can either be a string, an integer, a float, a complex number, or even a single item list of any of the above. There are no special characters to be escaped, but nested structures may be enclosed in square brackets to distinguish inner and outer separation characters.

• str

  Passed through.

• int, float, complex

  These types are converted according to the Python string representation.

• bool

  Boolean values are converted to the strings "true" or "false", lowercase, even though the capitalized versions and also "yes" and "no" are all supported in deserialization.

• bytes

  Bytes are converted to a base85 encoded string. Alternatively, if the bytes sequence matches an encoded unicode string, then this string prefixed with the encoding and a colon (like utf8:) is also valid (the colon is excluded from the base85 character set).

• datetime.date, datetime.time, datetime.datetime

  Date objects are converted to a string in ISO 8601 format.

• list[T], tuple[T, ...], tuple[T1, T2, T3]

  List items are comma joined. Any item that contains a comma in UCSL form is enclosed in square brackets.

  >>> ags.ucsl.dumps([["foo"], ["bar", "baz"]], list[list[str]])
  'foo,[bar,baz]'
  

  Note that, while dumps introduces the minimum amount of brackets, loads accepts them wherever they may occur, even if they are not required.

  >>> ags.ucsl.loads("[foo],[bar,baz]", list[list[str]])
  [['foo'], ['bar', 'baz']]
  

• dict[K, V]

  Dictionary items are comma joined, and the key and value equals joined. Any key that contains a comma or equals is enclosed in square brackets; so is any value that contains a comma.

  >>> ags.ucsl.dumps({"a=>z": [123], "foo": [4, 5]}, dict[str,list[int]])
  '[a=>z]=123,foo=[4,5]'
  

• typing.Optional or T|None

  An undefined optional value is represented by a single dash (-). Defined optional values are enclosed in brackets only if they convert to a dash.

• typing.Union or T1|T2|T3

  Unions of multiple types are converted to the name of the type followed by the object enclosed in square brackets. E.g., from the introduction:

  >>> ags.ucsl.dumps(items, L)
  'Point[value=1+2j,end=-],Axis[real],Point[value=1j,end=1.5]'
  

Other object types

In addition to the primitive object types mentioned above, the following objects are supported by first converting them to a primitive. As such, these rules are common to all backends:

• dataclasses.dataclass

  Data classes are converted to dictionaries based on their attribute annotations.

• enum.Enum

  Enum objects are identified by their name and converted to a string.

• inspect.Signature

  A function signature will not generally be used as a type annotation, but it is supported for dumping and loading of an inspect.BoundArguments instance. This is a convenient way of converting all arguments of a function to and from a dictionary.

• objects that define __into_ags__ and __from_ags__

  Any object can make itself suitable for AGS by defining two special methods that transform the object into and out of an alternative form which AGS does know how to handle. Here is an example of a custom class that is serilialized as a string:

  >>> from typing import Self
  >>>
  >>> class MyClass:
  ...     def __init__(self, s: str):
  ...         self.s = s
  ...     def __into_ags__(self) -> str:
  ...         return self.s
  ...     @classmethod
  ...     def __from_ags__(cls, s: str):
  ...         return cls(self.s)
  >>>
  >>> ags.json.dumps(MyClass("foo"), MyClass)
  '"foo"\n'
  

• objects that reduce to a single constructor argument (Python >= 3.11)

  Lastly, objects that reduce to their own class and a single argument are identified by that argument. This is very similar to the __into_ags__ method except that this also affects the way the object is pickled. It also requires a particular annotation for AGS to recognize the pattern, which is only available as of Python 3.11:

  >>> from typing import Self
  >>>
  >>> class MyClass:
  ...     def __init__(self, s: str):
  ...         self.s = s
  ...     def __reduce__(self) -> tuple[type[Self], tuple[str]]:
  ...         return MyClass, (self.s,)
  >>>
  >>> ags.json.dumps(MyClass("foo"), MyClass)
  '"foo"\n'