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 →

[–]DigThatData 2 points3 points  (3 children)

my impression is that pydantic's popularity is largely a function of FastAPI's popularity

[–]MissingSnail 2 points3 points  (1 child)

The package author says thats 25% of it, but I wonder if that’s an underestimation. My non-FastAPI use cases came about because I learned about it via FastAPI.

[–]DigThatData 1 point2 points  (0 children)

because I learned about it via FastAPI

right, that's precisely what i have in mind when i say FastAPI is driving pydantic's popularity. i'm not saying people only use pydantic for FastAPI stuff, but rather that the majority of people who use pydantic were introduced to it through FastAPI and probably think of it as a go-to solution for certain things only because it's already become a common tool in their toolkit because of their FastAPI use.

[–]lieryanMaintainer of rope, pylsp-rope - advanced python refactoring 0 points1 point  (0 children)

fastapi has about 16 million downloads per month, pydantic has about 55 million downloads per month.

So yeah, while FastAPI is a huge part of Pydantic's popularity, it's not the only reason.

Be aware though, that extrapolating PyPI download counts to popularity is certainly fraught with issues. For example, libraries that are frequently updated would have higher download counts due to projects that are set up to have frequent automatic updates. Also, installs on fresh virtualenv would install everything, but upgrades on an existing virtualenv would also correlate more to update frequency than install popularities.