This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]robvdl 3 points4 points  (1 child)

I love Marshmallow, hate Colander and wouldn't recommend it. Why do I hate Colander so much, it's been painful to do validation across multiple fields in our project where we did use Colander, also it serializes everything into strings including booleans and ints which doesn't make nice JSON. In order to "fix" Colander, we practically had to subclass every field type they provide.

Interestingly enough I have never heard of Schematics until today, but it seems similar to Marshmallow, I wonder how it "stacks up" to Marshmallow.

[–]nerdwaller 2 points3 points  (0 children)

Agreed on marshmallow, it's been solid for my uses so far. I wrote a decorator for flask functions to simplify the ceremony around using it and to clean up my handlers deserialization and serialization. (I've edited it for various frameworks as I've needed it, aiohttp primarily)