[issue30539] Make Proactor public in asyncio.ProactorEventLoop

Yury Selivanov added the comment: Big -1 from me. If proactor is public, alternative event loop implementations like uvloop will have to implement its full API, which actually puts restrictions on us refactoring asyncio itself. If there's some missing functionality we

[issue30539] Make Proactor public in asyncio.ProactorEventLoop

Andrew Svetlov added the comment: asyncio doesn't expose `loop.selector` and `loop.proactor` -- it is deliberate choice. What proactor methods are needed to serial support? Maybe we can incorporate them into event loop itself -- as we did for `loop.sock_*`?

[issue30539] Make Proactor public in asyncio.ProactorEventLoop

New submission from jabdoa: pyserial-asyncio cannot use IOCP for serial sockets on windows because _proactor is private on the ProactorEventLoop. Can it be made public? Currently, pyserial-asyncio has to rely on polling for windows which is suboptimal. Some forks use Proactor (e.g.