[Python-ideas] The async API of the future: yield-from
Steve.Dower at microsoft.com
Tue Oct 16 23:31:53 CEST 2012
> Yes, but in my world, there is only *one* scheduler.
> Just to be clear, I'm not saying there should only be one scheduler *implementation* in existence -- only that
> there should only be one *instance* of some scheduler implementation in any given program (or thread, if
> you're using those). And there should be a standard interface for it and an agreed way of finding the instance.
I agree with this entirely. There are a lot of optimisations to be had with different scheduler implementations, but the only way this can be portable is with a minimum supported interface and a standard way to find it.
More information about the Python-ideas