msgspec VS marshmallow

Full support for validation and serialisation of attrs classes and msgspec Structs. Where previously only Pydantic models and types where supported, you can now mix and match any of these three libraries. In addition to this, adding support for another modelling library has been greatly simplified with the new plugin architecture

> Maybe it was very slow before

That is at least partly the case. I maintain msgspec[1], another Python JSON validation library. Pydantic V1 was ~100x slower at encoding/decoding/validating JSON than msgspec, which was more a testament to Pydantic's performance issues than msgspec's speed. Pydantic V2 is definitely faster than V1, but it's still ~10x slower than msgspec, and up to 2x slower than other pure-python implementations like mashumaro.

Recent benchmark here: https://gist.github.com/jcrist/d62f450594164d284fbea957fd48b...

[1]: https://github.com/jcrist/msgspec

While it's definitely much faster than pydantic V1 (which is a huge accomplishment!), it's still not exactly what I'd call "fast".

I maintain msgspec (https://github.com/jcrist/msgspec), a serialization/validation library which provides similar functionality to pydantic. Recent benchmarks of pydantic V2 against msgspec show msgspec is still 15-30x faster at JSON encoding, and 6-15x faster at JSON decoding/validating.

Benchmark (and conversation with Samuel) here: https://gist.github.com/jcrist/d62f450594164d284fbea957fd48b...

This is not to diminish the work of the pydantic team! For many users pydantic will be more than fast enough, and is definitely a more feature-filled tool. It's a good library, and people will be happy using it! But pydantic is not the only tool in this space, and rubbing some rust on it doesn't necessarily make it "fast".

https://github.com/jcrist/msgspec so I am using this instead of Pydantic.

Another thing: why pyserde rather than stuff like msgspec? https://github.com/jcrist/msgspec

Try msgspec | Maat | turbo for fast serialization and validation

Congratulations to the team, Pydantic is an amazing library.

If you find JSON serialization/deserialization a bottleneck, another interesting library (with much less features) for Python is msgspec: https://github.com/jcrist/msgspec

This feature is yet to be released, but it will allow you to seamlessly use data modelled with for example Pydantic, SQLAlchemy, msgspec or dataclasses in your route handlers, without the need for an intermediary model; The conversion will be handled by the specific DTO "backend" implementation. This new paradigm also makes it trivial to add support for any such modelling library, by simply implementing an appropriate backend.

Somehow get a serializer going for your database models. I used marshmallow and flask-marshmallow

Uses a robust data validation library: validating payloads is a complex business. Your data validation library must handle optional and required properties, string formats like ISO dates and UUIDs (both dates and UUIDs are string types in OpenAPI), and strict vs loose type validation (should a string pass as an integer if it can be casted?). Also, in the case of Python, you need to make sure 1 and 0 don’t pass for True and False when it comes to boolean properties. In my experience, the best data validation libraries in the Python ecosystem are pydantic and marshmallow. From the above-mentioned libraries, flasgger and flask-smorest work with marshmallow.

I also came across things like Marsmallow and Blueprints, but don't know what these are, still reading about this as I write.

Pydantic is a data validation library, marshmallow is a data validation library. None of the other libraries in the list of pydantic alternatives is a data validation library.

I have been working on a package that is very similar in concept to marshmallow (https://marshmallow.readthedocs.io), but which adds a versioning mechanism to track changes in object structure across time, allowing you to migrate objects between different versions.

Either using meta programming: https://github.com/marshmallow-code/marshmallow/issues/585

You might be surprised how much I agree - I recently opened an issue there hoping to discuss something like this (still awaiting response). https://github.com/marshmallow-code/marshmallow/issues/2000

Marshmallow

I created a shallow fork of everyone's favourite marshmallow, to work around some performance issues while dumping data. The performance gain I measured is around 45%, but since it's a bad idea to rely on one's own testing, I was hoping that there are some folks here who use marshmallow in their projects, and who would be willing to try it out. Doubly so if your project has some unit tests in it, to confirm that nothing is broken due to my patches.

I was looking at https://github.com/marshmallow-code/marshmallow That's a nice library to use to parsing?