[Python-ideas] The async API of the future: yield-from
greg.ewing at canterbury.ac.nz
Sat Oct 20 01:29:25 CEST 2012
Calvin Spealman wrote:
> I think it is important that this is more than convention. I think that we
> need our old friend TOOOWTDI (There's Only One Obvious Way To Do It)
> here more than ever.
This is part of the reason that I don't like the idea of
controlling the scheduler by yielding instructions to it.
There are a great many ways that such a "scheduler instruction
set" could be designed, none of them any more obvious than
So rather than single out an arbitrarily chosen set of
operations to be regarded as primitives that the scheduler
knows about directly, I would rather have *no* such
primitives in the public API.
More information about the Python-ideas