New submission from Decorater: I use a library that uses run_until_complete that is used for HTTP connections. However it does not work well when you want to reconnect anything that makes it start via recursion. So, I am suggesting the removal of run_until_complete and then tell everyone that uses it to replace their code that had it with run_forever. ( and to have their start function to create a event loop so that way if the loop is closed recursing to restart it after closed would make it not throw a RuntimeError)
run_forever seems to be almost exactly alike run_until_complete except it can run forever. Pros with removing run_until_complete: + A lot easier to handle. + No pain from run_until_complete. + Cleanup some *code* in asyncio. + Helps with heavy http load for reconnecting websockets if they use run_forever instead. Cons: - Existing code from libs or anyone that uses run_until_complete will break. - run_forever can still throw a RuntimeError if you try to use run_forever after closing a event loop. - Event Loop would have to be recreated or reopened after being closed. ---------- components: asyncio messages: 272809 nosy: Decorater, gvanrossum, haypo, yselivanov priority: normal severity: normal status: open title: remove run_until_complete type: enhancement versions: Python 3.6 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue27770> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
