New submission from Yury Selivanov <yseliva...@gmail.com>: Currently, asyncio code accesses Future._loop and Task._loop property to validate the event loop and implement functions like "Task.all_tasks()". So the "_loop" is a semi-official public API that other Task & Future implementations must follow in order to be compatible with asyncio code.
I propose to add Future.get_loop() and Task.get_loop() methods, and soft-deprecate ._loop property. ---------- assignee: yselivanov components: asyncio messages: 308957 nosy: asvetlov, yselivanov priority: normal severity: normal status: open title: Add Task.get_loop() and Future.get_loop() versions: Python 3.7 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32415> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
