Marshmallow: Simplified object serialization for Python

Used it on a huge project where I wanted the interfaces clean between the Python project at runtime and to serialize the Python objects to the database. Using pickling gave me sleepless night until I moved to Marshmallow. Whilst Django REST Framework comes with a nice serializer and parser modules, marshmallow&#x27;s ability to do just the part was a godsend.<p>This alone gave us the flexibility to expose the Python modules and objects as a simple JSON API and the DB load &#x2F; save came for free.<p>Highly recommended.

Just wanted to say, this project has some of the best documentation around. Really happy to have this library around :)

Marshmallow is really useful. +1. If you like Marshmallow, you might also like Pilo (<a href="https:&#x2F;&#x2F;github.com&#x2F;eventbrite&#x2F;pilo" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;eventbrite&#x2F;pilo</a>), which solves similar problems. Marshmallow excels at ORM object serialization. Pilo is really good at parsing JSON into Python objects, and has several features to support this, such as polymorphic downcasting and programmable parsing via hooks. Marshmallow is also very good at parsing&#x2F;validating Python dictionaries, but in my experience, Marshmallow&#x27;s API is more focused on serializing objects into dictionaries so that you can call json.dumps on the output dictionary.

I&#x27;m also a fan of Schematics (<a href="https:&#x2F;&#x2F;schematics.readthedocs.org&#x2F;en&#x2F;latest&#x2F;" rel="nofollow">https:&#x2F;&#x2F;schematics.readthedocs.org&#x2F;en&#x2F;latest&#x2F;</a>) which is more or less identical in intent

I really hate this property magic, it was bad in the Django ORM and it&#x27;ll be bad in Marshmallow too. It looks nice in the examples, but then when you have to use it in anger and a certain problem requires metaclasses to fix...

Maybe object versioning can get added as this gains more and more usage... That will really make this a library that IMHO is production worthy; large applications can&#x27;t be easily upgraded in one-go and having a library that helps with translating across versions would be super.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;marshmallow-code&#x2F;marshmallow&#x2F;issues&#x2F;171" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;marshmallow-code&#x2F;marshmallow&#x2F;issues&#x2F;171</a> (if anyone is interested).

Awesome project. Using it on several customer projects (non public code) and probably soon on Abilian Platform.

I&#x27;m used to colander - <a href="http:&#x2F;&#x2F;colander.readthedocs.org&#x2F;en&#x2F;latest&#x2F;" rel="nofollow">http:&#x2F;&#x2F;colander.readthedocs.org&#x2F;en&#x2F;latest&#x2F;</a>

has anyone used ANY object serialization library (other than pickle) with multiprocessing ?<p>I just cant get anything else to work. We have a sophisticated desktop pyqt application that could really do with a better serialization with multiprocessing.<p>I have heard of Pathos[1] to replace multiprocessing - but never gave it a try.<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;uqfoundation&#x2F;pathos" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;uqfoundation&#x2F;pathos</a>

And then there is clojure where you just keep things as data all the time.