How Are Libraries in the Pure Python Web Application Survey Graded?

I was recently asked:

Looks like an amazingly detailed article! But I have to ask, it seems like there are some class A that are far less maintained and robust than Streamlit, what did you base the ranking on?


I would like to take a step back and say that incarnation 1 of this survey and incarnation 2 of this survey did not have grades. In those surveys, the libraries were classified by what they offered. However, for some reason, when doing this latest version of the survey, I wanted people to be able to find a solution they could trust.

So anyway, What does it take to be Class A?

To be class A, you have to be able to offer everything that you see in Miguel Grinberg’s Flask Mega Tutorial: sessions, authentication, authorization.

The whole idea is that Flask and Django are the best known solutions, so if you arent going to use them, you better be able to tell your client/boss that it is just as capable and yet easier to use because you only use Python.

So there you have it. So getting back to Streamlit, it makes dashboarding a piece of cake, but the route to all the functionality that a full-blown web app has does not appear to be easy as you can see from the discussion board here. That’s also why Dash is graded so low.

So what are the criteria?

Documentation, recency of commits to the source repo, size of community, quality of deliverables, age of product.

But none of this is done quantitatively: it’s all qualitative.

Leave a Reply

Your email address will not be published. Required fields are marked *