Skip to main content
Latest Version License Python Versions CI LINTER Coverage

Serialize: A common Python API for multiple serialization formats

There are multiple serialization formats out there ...
    ... and great packages to use them.

But they all have a different API and switching among them is not so simple as it should be. Serialize helps you to do it, including dealing with custom classes. Let’s dump a dict using the pickle format:

>>> from serialize import dumps, loads
>>> dumps(dict(answer=42), fmt='pickle')
b'\x80\x03}q\x00X\x06\x00\x00\x00answerq\x01K*s.'
>>> loads(_, fmt='pickle')
{'answer': 42}

And here comes the cool thing, you can just change the serialization format without having to learn a new API. Let’s now dump it using msgpack:

>>> dumps(dict(answer=42), fmt='msgpack')
b'\x81\xa6answer*'
>>> loads(_, fmt='msgpack')
{'answer': 42}

Serialize currently support 8 different formats: bson, dill, json (builtin or with simplejson package), msgpack, phpserialize, pickle, serpent and yaml. Serialize does not implement these formats but rather relies on established, well tested packages. If they are installed, serialize will use them.

** Serialize allows you to use them all with the same API! **

You can also use the dump and load to write directly to file-like object:

>>> from serialize import dump, load
>>> with open('output.yaml', 'wb') as fp:
...     dump(dict(answer=42), fp, fmt='yaml')
>>> with open('output.yaml', 'rb') as fp:
...     load(fp, fmt='yaml')
{'answer': 42}

or use directly the filename and the format will be inferred:

>>> dump(dict(answer=42), 'output.yaml')
>>> load('output.yaml')
{'answer': 42}

A very common case is to dump and load objects from custom classes such as:

>>> class User:
...     def __init__(self, name, age):
...         self.name = name
...         self.age = age
...
>>> john = User('John Smith', 27)

But some serialization packages do not support this important feature and the rest usually have very different API between them. Serialize provides you a common, simple interface for this. You just need to define a function that is able to convert the object to an instance of a builtin type and the converse:

>>> from serialize import register_class
>>> def user_to_builtin(u):
...     return (u.name, u.age)
...
>>> def user_from_builtin(c):
...     return User(c[0], c[1])
...

>>> register_class(User, user_to_builtin, user_from_builtin)

And that’s all. You can then use it directly without any hassle:

>>> dumps(john, fmt='bson')
b"y\x00\x00\x00\x03__bson_follow__\x00c\x00\x00\x00\x04__dumped_obj__
\x00\x1e\x00\x00\x00\x020\x00\x0b\x00\x00\x00John Smith\x00\x101\x00
\x1b\x00\x00\x00\x00\x02__class_name__\x00\x1c\x00\x00\x00<class '__m
ain__.Username'>\x00\x00\x00"
>>> v = loads(_, fmt='bson')
>>> v.name
'John Smith'
>>> v.age
27

Enjoy!

Metadata

Release files for Serialize 0.2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for Serialize 0.2.1
File Size Uploaded Provenance Actions
Serialize-0.2.1.tar.gz 14.7 kB Without provenance Details for Serialize-0.2.1.tar.gz

Release files / Serialize-0.2.1.tar.gz

Download URL Serialize-0.2.1.tar.gz
Size 14.7 kB
Tags Source
SHA-256 checksum
How to use checksums
d6610e0f513e87a76dd05947bedb3c85b7cc51bbd78f7775696ea4f55d9112dd
BLAKE2b-256 checksum
How to use checksums
9162d0fe3397a276e2586836c52e9c3eadc1bfd1a0641361cd7365bbe6dd612f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.7.0 importlib_metadata/4.8.1 pkginfo/1.8.2 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.7

Security for Serialize 0.2.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.2.1 This release

1 release file No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page