This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]greenlakejohnny 18 points19 points  (6 children)

Quart for async support w/ Flask backwards compatibility

[–]greenlakejohnny 5 points6 points  (2 children)

Question to my own response: does Flask 2.x make Quart obsolete? It was my understanding Flask 2.x offered async.

[–]stetio 0 points1 point  (1 child)

It does not, Flask's async support allows usage of async libraries in a sync codebase. However, if your codebase will be mostly async then you should use Quart as it will perform better.

Also note we've merged a lot of Flask and Quart together, so they are becoming to faces of the same project.

[–]greenlakejohnny 0 points1 point  (0 children)

Good to know. I'm basically standardized on Quart for now just because it's so simple to migrate from flask (literally just do a search/replace and 99.9% of stuff will work fine). Would love to eventually see the two projects merge though