[python-tulip] Re: Status of asyncio.readthedocs.io ?

2016-11-01 Thread Ludovic Gasc
Hi, FYI, I've did a workshop with 35 attendees during the Pycon-FR 2016 about AsyncIO and aiohttp.web. I used mainly http://asyncio.readthedocs.io/ as course support. I'm not a professional trainer, nevertheless, everybody seem to be happy. My main advice is to ask at the beginning of the sessio

[python-tulip] Re: [tornado] Re: Announcing Motor 0.7, async MongoDB driver for Tornado and asyncio

2016-11-01 Thread A. Jesse Jiryu Davis
In my own benchmark, which was admittedly contrived for the sake of showing the best possible improvement, the new code is 30% faster. On Tue, Nov 1, 2016 at 4:23 PM, Lazaro Aulan wrote: > Thank for Motor. > > Has anyone noticed any change in how fast it is now. > Any test? > > > среда, 26 октяб

Re: [python-tulip] Explicit vs Implicit event loop

2016-11-01 Thread Yury Selivanov
> On Nov 1, 2016, at 10:46 AM, Andrew Svetlov wrote: > > The same problem is present in asyncio classes itself: Lock, Queue, streams > could be created with global life time and they are will hang if used from > different loop. Once we fix get_event_loop we can guard against this in debug mod

Re: [python-tulip] Explicit vs Implicit event loop

2016-11-01 Thread Andrew Svetlov
On Monday, October 31, 2016 at 6:27:57 PM UTC+2, Guido van Rossum wrote: > > It's an interesting problem. I would like to rephrase your conclusion: > the implicit loop should only be used when the object you are creating > has a shorter (or equal) lifetime than the loop. I would also think > t

Re: [python-tulip] Discussion thread for: http://lucumr.pocoo.org/2016/10/30/i-dont-understand-asyncio/

2016-11-01 Thread Artur Wroblewski
On Nov 1, 2016 2:16 AM, wrob...@riseup.net wrote: > > On 2016-10-30 17:58, Guido van Rossum wrote: > > Regarding the documentation, I doubt we can get it in shape just by > > filing issues. We should really just have a tutorial written by > > someone with a good understanding of asyncio and writing