title: Flask vs webapp2 for Google App Engine
body: <p>I'm starting new Google App Engine application and currently considering two frameworks: <a href="http://flask.pocoo.org/" rel="noreferrer">Flask</a> and <a href="http://webapp-improved.appspot.com/" rel="noreferrer">webapp2</a>. I'm rather satisfied with built-in webapp framework that I've used for my previous App Engine application, so I think webapp2 will be even better and I won't have any problems with it.</p>
  
  <p>However, there are a lot of good reviews of Flask, I really like its approach and all the things that I've read so far in the documentation and I want to try it out. But I'm a bit concerned about limitations that I can face down the road with Flask.</p>
  
  <p>So, the question is - <em>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?</em> By "problem" I mean something that I can't work around in several lines of code (or any reasonable amount of code and efforts) or something that is completely impossible.</p>
  
  <p>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?</p>