I'm a big fan of flask, purely because there's no wrangling `request` objects down your stack, and you can just fish it out later when you need it.
My main complaint would be Flask's 'extensions'. I'm really not a fan of the
> app = Flask(__name__) > db = Database(app)
pattern. it makes getting your db back later a little trickier. It would be nice if the `Flask` instance held it for you, so you could get it back with `flask.current_app` later.
It further doesn't work when the plugin provides a sets of views (i.e. CRUD) e.g.
> app = Flask(__name__) > crud = CrudPlugin(app)
I've yet to see a case of why this isn't implemented as a blueprint.