dacite

To solve this they introduce another, but more obscure, third party dependency called `dacite`, that converts `pydantic` to `dataclasses`.

But then adds dacite to translate between pydantic at the border and python objects internally.

Consequently they are not generally explosive in the way volcanoes with higher viscosity lavas (higher silica content) like andesite or dacite are.

I have never seen dacite, but it’s pretty easy for a small library to just be complete.

I've also looked at similar libraries like Dacite and marshmallow-dataclasses but none seem to be well thought out and mature.

It's more likely that `dacite` is going to break your application, than `pydantic`, a library used by millions of users in huge projects, ever will.

I recommend starting with obsidian or dacite, they are much easier than flint and chert.

You should look into the 'dacite' library!

Adding a random dependency `dacite`, which has 1.9k Github stars, no one has ever heard of, and was last updated 4 months ago, introduces way more complexity and sources of instabilities than propagating `pydantic`.

Dacite and marshmallow-dataclasses don't support generics well either, with some issues around Union types.

Obscure third party dependencies (Dacite) Thanks, I'll pass.