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

> On Oct 30, 2016, at 3:00 PM, Donald Stufft wrote: > > >> On Oct 30, 2016, at 5:36 PM, Guido van Rossum > > wrote: >> >> But if you want HTTP, you really should use aiohttp, not some crappy >> version that we might supply in the stdlib. There's nothing >> dishonorable

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

Such a tutorial would be fine as a HOWTO (in https://docs.python.org/3/howto/index.html) but IMO not in the stdlib docs for asyncio itself (there could be a pointer to the HOWTO doc of course). Then again the stdlib docs don't need to be a tutorial. Skimming Armin's blog it seems one problem is th

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

> On Oct 30, 2016, at 3:02 PM, Yury Selivanov wrote: > > I’ve just looked through events.py. I think we may only need to add > “asyncio.run_in_executor(func)”, and maybe “asyncio.create_task(coroutine)” > functions. With that it should be possible to have almost the same > “loopless” experi

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

> On Oct 30, 2016, at 5:36 PM, Guido van Rossum wrote: > > But if you want HTTP, you really should use aiohttp, not some crappy > version that we might supply in the stdlib. There's nothing > dishonorable about using a 3rd party package! Maybe it would make sense to use aiohttp or something t

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

On Sun, Oct 30, 2016 at 12:28 PM, Luciano Ramalho wrote: > I found asyncio really daunting. Writing about it in Fluent Python was > by far the hardest part in the book -- and my goal was really modest, > just explain some very, very basic examples. I was glad to have Victor > Stinner review that c

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

Hello, As far as I understand, Armin’s starting point was “I want to understand everything about asyncio in order to support it well in Sentry”. This is higher bar than “I want to write decent asyncio code to get $X done”. I suspect that explains the absurd list of “things that you need to know

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

I found asyncio really daunting. Writing about it in Fluent Python was by far the hardest part in the book -- and my goal was really modest, just explain some very, very basic examples. I was glad to have Victor Stinner review that chapter in my book, so no major problems were reporded by readers s

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

> On Oct 30, 2016, at 2:42 PM, Guido van Rossum wrote: > > On Sun, Oct 30, 2016 at 11:27 AM, Yury Selivanov wrote: >> >>> On Oct 30, 2016, at 1:58 PM, Guido van Rossum wrote: >>> >>> Regarding the documentation, I doubt we can get it in shape just by >>> filing issues. We should really just

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

On Sun, Oct 30, 2016 at 11:27 AM, Yury Selivanov wrote: > >> On Oct 30, 2016, at 1:58 PM, 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 as

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

> On Oct 30, 2016, at 1:58 PM, 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 skills. Yeah, I agree. I don’t want to pro

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

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 skills. I wonder how enlightening the chapter by A. Jesse Jiryu Davis here really is for beginners? http://ao

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

I think there are some valid, as well as not so valid, points in that blog post. One thing for sure: we need to restructure the documentation. Anyways, I’ll try to go through the blog post in detail and create issues to address some things. Yury > On Oct 30, 2016, at 1:29 PM, Justin Mayfield

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

Armin is a great programmer but he is a well-known curmudgeon when it comes to anything related to Python 3. On Sun, Oct 30, 2016 at 10:29 AM, Justin Mayfield wrote: > I'm curious what a more localized discussion about this blog post looks > like. Personally I find it difficult to sympathize wit

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

I'm curious what a more localized discussion about this blog post looks like. Personally I find it difficult to sympathize with many of the arguments and have been a very happy user of modern python and asyncio for quite a while. The blog: http://lucumr.pocoo.org/2016/10/30/i-dont-understand-a