Ok, that makes sense, thanks! On Sunday, January 18, 2015, Guido van Rossum <gu...@python.org> wrote:
> Yes. It's a bit like memory allocation -- if you don't own it, don't free > it. > > On Sun, Jan 18, 2015 at 3:41 PM, Luciano Ramalho <luci...@ramalho.org > <javascript:_e(%7B%7D,'cvml','luci...@ramalho.org');>> wrote: > >> Like Victor Stinner in this bug report [1], I was craving for a >> context-manager enabled loop so I did not forget to close() it. >> >> But reading Guido's last message rejecting that bug, it seems callign >> loop.close() is only recommended "if you own the loop" -- while most >> asyncio users probably don't "own" it. >> >> [1] http://bugs.python.org/issue19860#msg205062 >> >> Can I conclude that in practice, close() should not be called at all >> unless your own code actually created the loop instead of merely >> fetching it with asyncio.get_event_loop()? >> >> Is that a sensible recommendation? >> >> Cheers, >> >> Luciano >> >> >> >> -- >> Luciano Ramalho >> Twitter: @ramalhoorg >> >> Professor em: http://python.pro.br >> Twitter: @pythonprobr >> > > > > -- > --Guido van Rossum (python.org/~guido) > -- Luciano Ramalho Twitter: @ramalhoorg Professor em: http://python.pro.br Twitter: @pythonprobr
