On Sat, Jun 13, 2020 at 7:29 AM J. Pic <[email protected]> wrote: > > I mean, if it pauses because of some blocking IO and switches to another > coroutine, that's just a BIG win ... I have hard times trying to figure how > that signal could be useful to me as a developer. On the other hand, I have > to (await test()).bar ... >
Exactly what threading is for. If you don't care where the context switches happen and just want everything to behave sanely by default, use threads, not coroutines. The entire point of coroutines is that you know exactly where they can switch contexts. ChrisA _______________________________________________ Python-ideas mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/TCDLNOHV5FDICKMKMALIGNKGKGZ6QA22/ Code of Conduct: http://python.org/psf/codeofconduct/
