In general you don't need a policy for every loop implementation. In a typical program you only have one event loop and it's no more work to just create a ProactorEventLoop instance than it is to create a policy. (See the examples -- several have an --iocp flag to force this.)
The other issue was my mistake -- I was pretty out of it yesterday (been feeling sick lately) and the PEP answered my question. On Sun, Jul 13, 2014 at 7:57 AM, Victor Stinner <[email protected]> wrote: > Hi, > > While documenting limitations on Windows and ran some tests on > Windows, I saw that there is no event loop policy for the > ProactorEventLoop. Is it a choice or we just forgot it? > > By the way, Guido asked me if get_event_loop() is supposed to return > None or raise an error if there is no event loop in the current > thread. > > Victor > -- --Guido van Rossum (python.org/~guido)
