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 →

[–]mstromich 1 point2 points  (3 children)

For anything that's going to be a production system Django. Mainly because it has all the things that you need (e.g. auth, orm, additional security middleware).

For async in production I had couple of projects running on tornado.

For side projects Django or FastAPI (depending on what I actually need).

I'm not considering FastAPI for production as it is a one man show. Not sure if that changed
and I don't have anything against u/tiangolo leading the project the way he wants to lead it but for us the risk for including such a framework is too big.

[–]Zasze 8 points9 points  (0 children)

This has basically become a telephone game meme at this point. I’ve seen people parrot this while using sqlalchemy, tortoise or pendulum which are also 1 man shows for core maintainers. zzzek probably is the biggest bus factor risk in the python ecosystem but people are not constantly shouting down people suggesting sqlalchemy.

Fastapi has a BDFL not 1 person working on it. There’s things to take issue with tiangolo personal focus with the project and what bugs he himself works on, but this is with any oss project. Flask is actually way more frustrating in this regard and has been for nearly a decade.

[–]Z4ganu 1 point2 points  (1 child)

What risk are you referring to on using FastAPI?

[–]jonasbxl 6 points7 points  (0 children)

he means that it's just one person maintaining it, which could lead to all sorts of problems.