Hi,
2014-02-13 20:39 GMT+01:00 Guido van Rossum :
> I think there should be no references to tracemalloc in the asyncio package;
> instead, there should be a hook (maybe the error handler that Yuri is
> adding???) so tracemalloc fans can help themselves.
My patch was just a proof-of-concept (usin
On 16 févr. 2014, at 16:02, Jonathan Slenders
wrote:
> I think that integration is indeed the way to go. No point to implement yet
> another complete web stack in asyncio.
FYI I’ve written the equivalent for Django [1] and discussed at length the
limitations [2].
[1] https://github.com/aaugu
Doh, the link is https://github.com/mrdon/flask
Don
On Sun, Feb 16, 2014 at 9:25 AM, Don Brown wrote:
> 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 i
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, ch
That looks nice.
I think that integration is indeed the way to go. No point to implement yet
another complete web stack in asyncio.
But make sure that WSGIServerHttpProtocol can also handle blocking code.
Most existing Flask applications still have blocking ORM code, and you
don't want such co
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
