STINNER Victor <vstin...@python.org> added the comment: > In modern asyncio code the explicit loop arguments are no longer used since > the loop can always be obtained with get_running_loop().
Yeah, the trend changed. Around Python 3.4, passing explicitly loop was preferred for best performances. Since that time, the code to get the current loop has been optimized, and the new trend is to make the loop implicit to make the code more readable. -- When I wrote the doc, self.loop.stop() was called explicitly: https://docs.python.org/3.5/library/asyncio-protocol.html#tcp-echo-client-protocol It seems like the example has been modified to add a new "on_con_lost" Future. -- Anyway, thanks Hrvoje Nikšić for your contribution ;-) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue38178> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
