I&#39;m starting new Google App Engine application and currently considering two frameworks: [Flask][1] and [webapp2][2]. I&#39;m rather satisfied with built-in webapp framework that I&#39;ve used for my previous App Engine application, so I think webapp2 will be even better and I won&#39;t have any problems with it.

However, there are a lot of good reviews of Flask, I really like its approach and all the things that I&#39;ve read so far in the documentation and I want to try it out. But I&#39;m a bit concerned about limitations that I can face down the road with Flask.

So, the question is - *do you know any problems, performance issues, limitations (e.g. routing system, built-in authorization mechanism, etc.) that Flask could bring into Google App Engine application?* By &quot;problem&quot; I mean something that I can&#39;t work around in several lines of code (or any reasonable amount of code and efforts) or something that is completely impossible.

And as a follow-up question: are there any killer-features in Flask that you think can blow my mind and make me use it despite any problems that I can face?


  [1]: http://flask.pocoo.org/
  [2]: http://webapp-improved.appspot.com/

All Webapp2 Solutions on Gang of Coders

Total of 1 Webapp2 Solutions

Flask vs webapp2 for Google App Engine