Wow Guido reads fast! I'm still about 25% into the post (2 days later), and yes, it's a very diligent, sensible write-up; I'd love to see more discussion about async cancellation and it-should-just-work :) Where is it held? Perhaps asyncio is not that popular yet? * 80K "asyncio" hits on github +code +python # roughly equal to bottle * 25K "aiohttp", only 7K "ensure_future" # marginal? (for comparison 3M hits for "requests" and 15M hits for "django")
What can I or we do to get developers to test these frameworks and validate ease of use and expected behaviour? Presentations? Hackatons? Bottom-up? Top-down? d. On 21 April 2017 at 02:53, Guido van Rossum <gu...@python.org> wrote: > Nice. Maybe someone can contribute a similar patch to asyncio? > > On Thu, Apr 20, 2017 at 5:11 PM, Nathaniel Smith <n...@pobox.com> wrote: > >> Hi async-sig, >> >> Some of you have probably already seen this, but in case it's of >> interest, I just posted some discussion of signal handling and how I >> approach it in trio: >> >> https://vorpus.org/blog/control-c-handling-in-python-and-trio/ >> >> If nothing else at least it's the signal handling documentation that I >> wish I had when I started :-). >> >> -n >> >> -- >> Nathaniel J. Smith -- https://vorpus.org >> _______________________________________________ >> Async-sig mailing list >> Async-sig@python.org >> https://mail.python.org/mailman/listinfo/async-sig >> Code of Conduct: https://www.python.org/psf/codeofconduct/ >> > > > > -- > --Guido van Rossum (python.org/~guido) > > _______________________________________________ > Async-sig mailing list > Async-sig@python.org > https://mail.python.org/mailman/listinfo/async-sig > Code of Conduct: https://www.python.org/psf/codeofconduct/ > >
_______________________________________________ Async-sig mailing list Async-sig@python.org https://mail.python.org/mailman/listinfo/async-sig Code of Conduct: https://www.python.org/psf/codeofconduct/
