Yanghao Hua <yanghao...@gmail.com> added the comment:
by the way, another feedback, of course, curio works the way it should, no matter where do you await ;-) Now I start to understand why David Beazley has to create curio. Python asyncio team should really really think about it carefully, please. You don't have to modify create_task(), at least a sane version (maybe create_task_sane()) could be provided. On Tue, Apr 6, 2021 at 10:46 AM Andrew Svetlov <rep...@bugs.python.org> wrote: > > > Andrew Svetlov <andrew.svet...@gmail.com> added the comment: > > 1. Please consider `await` as a 'yield point': the point where the current > task may be suspended to get other tasks a chance to be executed. > It can be any `await`, not necessarily waiting for a task. Just a point > where asyncio event loop gives a chance to roll an iteration. > > Note: no suspension happens if the argument is 'ready' already. > > 2. If we design asyncio from scratch we can consider the separation of task > creation and start. Unfortunately, the ship has sailed many years ago. The > behavior cannot be changed without breaking virtually every asyncio program, > sorry. > > ---------- > resolution: remind -> not a bug > stage: -> resolved > status: open -> closed > > _______________________________________ > Python tracker <rep...@bugs.python.org> > <https://bugs.python.org/issue43736> > _______________________________________ ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue43736> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
