[Python-ideas] Async API: some code to review

[Guido van Rossum]

On Mon, Oct 29, 2012 at 4:26 PM, Steve Dower <Steve.Dower at microsoft.com> wrote:
> Greg Ewing wrote:
>> Steve Dower wrote:
>>
>>>  - how easy/difficult/flexible/restrictive is it to write a new scheduler as an end user?
>>
>> I don't think that writing new schedulers is something an end user will do very often. Or
>> more precisely, it's not something they should *have* to do except in extremely
>> unusual circumstances.
>>
>> I believe it will be possible to provide a scheduler in the stdlib that will be satisfactory
>> for the vast majority of applications.
>
> I agree, and I chose my words poorly for that point: "library/framework developers" is more accurate than "end user". And since I expect every GUI framework is going to need (or at least want) their own scheduler, not to mention all the cases of Python being embedded in other programs, there is some value in helping these developers to get it right by virtue of the design rather than relying on documentation.

BTW, would it be useful to separate this into pollster, eventloop, and
scheduler? At least in my world these are different; of these three,
only the pollster contains platform-specific code (and then again the
transports do too -- this is a nice match IMO).

-- 
--Guido van Rossum (python.org/~guido)