On Fri, May 1, 2015 at 1:22 PM, Antoine Pitrou <solip...@pitrou.net> wrote:
> On Fri, 1 May 2015 13:10:01 -0700 > Guido van Rossum <gu...@python.org> wrote: > > On Fri, May 1, 2015 at 12:48 PM, Jim J. Jewett <jimjjew...@gmail.com> > wrote: > > > > > If there are more tasks than executors, yield is a way to release your > > > current executor and go to the back of the line. I'm pretty sure I > > > saw several examples of that style back when coroutines were first > > > discussed. > > > > > > > Could you dig up the actual references? It seems rather odd to me to mix > > coroutines and threads this way. > > I think Jim is saying that when you have a non-trivial task running > in the event loop, you can "yield" from time to time to give a chance > to other events (e.g. network events or timeouts) to be processed > timely. > > Of course, that assumes the event loop will somehow priorize them over > the just yielded task. > Yeah, but (unlike some frameworks) when using asyncio you can't just put a plain "yield" statement in your code. You'd have to do something like `yield from asyncio.sleep(0)`. -- --Guido van Rossum (python.org/~guido)
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
