Nice. I ended up forking Flask and Werkzeug to sprinkle "yield from" around as well as fix app.run:
https://bitbucket.org/mrdon/flask I'm certainly not a fan of this approach but it is working and letting me develop sync or async web apps pretty easily. Don On Sun, Feb 16, 2014 at 7:06 AM, chrysn <[email protected]> wrote: > hello python-tulip list, > > i've played around with aiohttp and flask/werkzeug/pocoo (an wsgi based > classical python web framework), and found that they can be made to play > nicely with each other easily. some features of the werkzeug framework > are sidestepped, i'm waiting for the developers' feedback to see how bad > it is. > > the demo code can be fetched from [1], the discussion on > [email protected] is archived at [2]. > > what are your opinions on this? if it works out, is there still a need > for dedicated asyncio web frameworks, apart from the lowest layer that > provides a wsgi+async interface? > > if the topic fits here, i'd like to keep this thread updated if relevant > information comes back from the pocoo people. > > best regards, > and thank you all for providing this cool new python base technology > > chrysn > > [1] https://www.gitorious.org/aiohttp-werkzeug-demo/aiohttp-werkzeug-demo/ > [2] https://groups.google.com/forum/#!topic/pocoo-libs/mTS1X7hfnkk > > -- > To use raw power is to make yourself infinitely vulnerable to greater > powers. > -- Bene Gesserit axiom >
