> On Oct 30, 2016, at 3:00 PM, Donald Stufft <[email protected]> wrote: > > >> On Oct 30, 2016, at 5:36 PM, Guido van Rossum <[email protected] >> <mailto:[email protected]>> 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 to explain the concepts > of AsyncIO instead of restricting it to just what’s in the standard library? > We have pip shipped w/ Python now and the venv module exists, so for most > people installing aiohttp into a virtual environment or something to play > with asyncio shouldn’t be a big deal. > > To be clear, I don’t mean try to extensively document aiohttp, but rather use > it as a real-ish world introduction to asyncio for folks.
Just as a data-point for this, I've been doing a few Twisted tutorials lately and we have taken a new tack which is to use Klein <https://github.com/twisted/klein> and Treq <https://github.com/twisted/treq> as real-world examples rather than restrict ourselves to what's in Twisted proper. This has been a _huge_ success in terms of comprehensibility for newcomers; the concrete example that you can make a browser talk to is much easier to explain than the highly abstract "example" Deferreds that we have used in the past. Some of the students at such tutorials would say stuff like "Actually I wanted to do something with IRC and IMAP, not a web app, but this gave me a much clearer idea of how to approach it." So I think having asyncio's tutorial work this way would probably be a big win. -glyph
