Python web micro-framework battle

Line count is a silly way to score when all are around the same anyway (fewer than 100 lines). And the framework line count is another metric that shouldn't matter.

That said, really the only valid point here against Flask is Python 3 support. Other than that Bottle and Flask are pretty much on par with each other.

Re: Python web micro-framework battle

#5

Post by mhd » Sun, Aug 28, 2011, 11:26 AM UTC

wyclif wrote: post #3

tl;dr: Bottle wins.

I think the scoring part (being very particular to the tester and not weighted at all) is the least interesting part of the presentation, the code and the comments for each framework are actually quite interesting. I just wish that Twisted / Tornade would've been in the fray.

Re: Python web micro-framework battle

#6

Post by puredemo » Sun, Aug 28, 2011, 11:33 AM UTC

Pesto wins if you count the extra features at the end.

Re: Python web micro-framework battle

#7

Post by nnythm » Sun, Aug 28, 2011, 11:54 AM UTC

Discounting pyramid as a microframework doesn't seem valid, given that it can be scaled up or down arbitrarily. https://docs.pylonsproject.org/projects/pyramid/1.2/ has an extremely concise pyramid web app above the fold.

Re: Python web micro-framework battle

#8

Post by MostAwesomeDude » Sun, Aug 28, 2011, 12:03 PM UTC

llambda wrote: post #4

Line count is a silly way to score when all are around the same anyway (fewer than 100 lines). And the framework line count is another metric that shouldn't matter. That said, really the only valid point here against Flask is Python 3 support. Other than that Bottle and Flask are pretty much on par with each other.

Flask has the advantages of fast templates, strong WSGI features, serious unit testability at the app and library level, complete documentation...

Re: Python web micro-framework battle

#9

Post by llambda » Sun, Aug 28, 2011, 12:06 PM UTC

MostAwesomeDude wrote: post #8

llambda wrote: post #4

Line count is a silly way to score when all are around the same anyway (fewer than 100 lines). And the framework line count is another metric that shouldn't matter. That said, really the only valid point here against Flask is Python 3 support. Other than that Bottle and Flask are pretty much on par with each other.

Flask has the advantages of fast templates, strong WSGI features, serious unit testability at the app and library level, complete documentation...

Don't get me wrong, I love Flask. It's become my go-to web framework for Python. In my opinion it wins. But, that's just my opinion. :)

Re: Python web micro-framework battle

#10

Post by LeafStorm » Sun, Aug 28, 2011, 1:56 PM UTC

I don't think counting Python 3 support is really important for Web frameworks. All of the major server distros are still on Python 2.x anyway (last I checked, Arch is the only one where "pacman -S python" will get you Python 3 instead of 2), and the question of WSGI is still up in the air if you want to handle encoding properly instead of just fudge it.