> On 03 Oct 2016, at 23:32, Greg Ewing <greg.ew...@canterbury.ac.nz> wrote: > > Yann Kaiser wrote: >> The way I see it, the great thing about async/await as opposed to threading >> is that it is explicit about when execution will "take a break" from your >> function or resume into it. > > Another thing is that async/await tasks are very lightweight > compared to OS threads, so you can afford to have a large > number of them active at once. > > Rene's approach seems to be based on ordinary threads, so > it would not have this property.
My implementation is, but it should not (have to) be, it only reflects my limited ability and time :-) The programmer should not need to be aware of where concurrency is achieved though coroutines or threads, ideally there should be one OS thread per core in the CPU running many (millions) of coroutines… br /Rene > > -- > Greg > _______________________________________________ > Python-ideas mailing list > Python-ideas@python.org > https://mail.python.org/mailman/listinfo/python-ideas > Code of Conduct: http://python.org/psf/codeofconduct/ _______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
