For one time, while we are in a congratulations tunnel, thank you a lot AsyncIO core devs:
Since several months, we've pushed on production an average of 2 daemons based on AsyncIO in my company with several protocols. Most of the time there are small daemons, however, some are complex. For now, the AsyncIO toolbox is pretty stable and predictive, especially for the debugging. The maturity is better that I've excepted, especially when you list the AsyncIO ecosystem: We are for now few developers to use that for "concrete" applications. At least to me, it's the best proof that the foundations are good. We should now try to publish more tutorials/examples to attract more newcomers, but I'm the first guilty: I'm completely lack of time to do that. BTW, I hope that EuroPython will be a good event to propagate some good vibes around AsyncIO. -- Ludovic Gasc (GMLudo) http://www.gmludo.eu/ 2015-06-25 22:24 GMT+02:00 Victor Stinner <victor.stin...@gmail.com>: > Hi, > > 2015-06-25 19:25 GMT+02:00 Andrew Svetlov <andrew.svet...@gmail.com>: > > P.S. > > Thank you Victor so much for your work on asyncio. > > Your changes on keeping source tracebacks and raising warnings for > > unclosed resources are very helpful. > > Ah! It's good to know. You're welcome. > > We can still enhance the source traceback by building it using the > traceback of the current task. > > Victor > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/gmludo%40gmail.com >
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
