
Yesterday (27-Sep-2015), four Washington DC area Python developers got together for a local Python hacking sprint. Andrew, Eric, Jason, and I were joined remotely by the esteemed R. David Murray. We did stuff and had fun! We hope to do stuff and have fun again! If you want to join us for stuff and fun next time, please get in touch. Here's a write-up of the sprint: https://gitlab.com/python-smtpd-hackers/aiosmtpd/wikis/2015-09-27-hackfest Special thanks to the PSF and Brian Curtin for sponsoring the sprint. Cheers, -Barry

Cool! Glad to see that the idea of local core-dev sprints hasn't totally been forgotten. I saw that you had a need for an asyncio tutorial. I wonder if the "500 lines" chapter on asyncio would help? I didn't write it; I only write the 500 lines of code, A. Jesse Jiryu Davis wrote the text, and it's wonderful: http://aosabook.org/en/500L/a-web-crawler-with-asyncio-coroutines.html On Mon, Sep 28, 2015 at 7:32 AM, Barry Warsaw <barry@python.org> wrote:
-- --Guido van Rossum (python.org/~guido)

I would like to propose a mixed core-dev none-core-dev sprint to occur in Chicago within the next couple months. ChiPy (http://chipy.org) can help sponsor. I am going to share my thoughts on this with the group-organizers < group-organizers@python.org> list first in order to get some feedback. Post found here: https://mail.python.org/pipermail/group-organizers/2015-September/000441.htm Regards, Brian Ray ChiPy organizer

On Sep 28, 2015, at 08:22 AM, Guido van Rossum wrote:
It's a great article, and I particularly like how it starts from first principles and builds essentially the asyncio framework up from them, with nice explorations on how things like generators work. But it's not quite what I'm looking for. When I go to the stdlib asyncio docs page, I'm immediately thrown into (albeit good) reference documentation. I though that the page "Develop with asyncio" might give me what I want, but it's really not. What I'm looking for is a gentle introduction, assuming that the reader either understands the basics of asynchronous i/o or maybe comes from a background in threaded programming. It would then explain things like "this is a Future and this is what you use it for", "this is a Task and this is when you use a Task and when you use a Future", "this is when you want to define a Protocol, and this is how it hooks into the framework". I think that kind of high-level overview of the classes and how they hang together is what I think is missing. Take for example 18.5.3 Tasks and coroutines. Aside from the fact that the title would imply it would start explaining Tasks, it actually doesn't get to them until way later on the page! What's a Future? The first thing the asyncio page says is that the "class is almost compatible with concurrent.futures.Future". Okay, but that still doesn't tell me what it *is* or what it's used for. Following the link to that other class isn't really enlightening. ;) I hope my comments make sense. I know that when you already understand the concepts, it's difficult to distill them into the right documentation for very different audiences. What's there seems mostly great for reference, and maybe the stdlib docs aren't the right place for what I want, but as the 500 Lines chapter promotes, asyncio is pretty powerful so it would be nice to have Python documentation for newcomers. I'm sure I'm not the right person to write it though. ;) Cheers, -Barry

Sent from my iPhone
I think you'd be a great person to write those docs -- in partnership with someone that really understands the guts. The first step to docs is knowing what questions to answer, and in what order to answer them. You've recently gone through the process of trying to figure it out for a particular use case -- you know just what questions you had. And you even just posted the start of an outline..... Whether that's what you want to do with your limited time is another question... CHB

Cool! Glad to see that the idea of local core-dev sprints hasn't totally been forgotten. I saw that you had a need for an asyncio tutorial. I wonder if the "500 lines" chapter on asyncio would help? I didn't write it; I only write the 500 lines of code, A. Jesse Jiryu Davis wrote the text, and it's wonderful: http://aosabook.org/en/500L/a-web-crawler-with-asyncio-coroutines.html On Mon, Sep 28, 2015 at 7:32 AM, Barry Warsaw <barry@python.org> wrote:
-- --Guido van Rossum (python.org/~guido)

I would like to propose a mixed core-dev none-core-dev sprint to occur in Chicago within the next couple months. ChiPy (http://chipy.org) can help sponsor. I am going to share my thoughts on this with the group-organizers < group-organizers@python.org> list first in order to get some feedback. Post found here: https://mail.python.org/pipermail/group-organizers/2015-September/000441.htm Regards, Brian Ray ChiPy organizer

On Sep 28, 2015, at 08:22 AM, Guido van Rossum wrote:
It's a great article, and I particularly like how it starts from first principles and builds essentially the asyncio framework up from them, with nice explorations on how things like generators work. But it's not quite what I'm looking for. When I go to the stdlib asyncio docs page, I'm immediately thrown into (albeit good) reference documentation. I though that the page "Develop with asyncio" might give me what I want, but it's really not. What I'm looking for is a gentle introduction, assuming that the reader either understands the basics of asynchronous i/o or maybe comes from a background in threaded programming. It would then explain things like "this is a Future and this is what you use it for", "this is a Task and this is when you use a Task and when you use a Future", "this is when you want to define a Protocol, and this is how it hooks into the framework". I think that kind of high-level overview of the classes and how they hang together is what I think is missing. Take for example 18.5.3 Tasks and coroutines. Aside from the fact that the title would imply it would start explaining Tasks, it actually doesn't get to them until way later on the page! What's a Future? The first thing the asyncio page says is that the "class is almost compatible with concurrent.futures.Future". Okay, but that still doesn't tell me what it *is* or what it's used for. Following the link to that other class isn't really enlightening. ;) I hope my comments make sense. I know that when you already understand the concepts, it's difficult to distill them into the right documentation for very different audiences. What's there seems mostly great for reference, and maybe the stdlib docs aren't the right place for what I want, but as the 500 Lines chapter promotes, asyncio is pretty powerful so it would be nice to have Python documentation for newcomers. I'm sure I'm not the right person to write it though. ;) Cheers, -Barry

Sent from my iPhone
I think you'd be a great person to write those docs -- in partnership with someone that really understands the guts. The first step to docs is knowing what questions to answer, and in what order to answer them. You've recently gone through the process of trying to figure it out for a particular use case -- you know just what questions you had. And you even just posted the start of an outline..... Whether that's what you want to do with your limited time is another question... CHB
participants (4)
-
Barry Warsaw
-
Brian Ray
-
Chris Barker - NOAA Federal
-
Guido van Rossum