QEventLoopPolicy to manage multiple event loops (one per thread) about quamash HOT 1 OPEN

I've only just discovered quamash, so I may be missing some context, but IMO, it should absolutely provide an event loop policy. That is the standard interface for switching event loop implementations, not simply setting one specific event loop as is expected now.

1. As it's the standard, some async frameworks (asphalt is the one I happen to be working with at the moment) explicitly support passing or registration of event loop policies.
2. Not having a policy creates an error-prone situation where the currently-set event loop policy may create loops of other types, leading to breakage (this situation is only saved for most current cases by pure coincidence, as the "default" event loop policy in the stdlib doesn't implicitly create additional event loops beyond the main one, but that may not be, and probably isn't, the case for other third-party event loop implementations). If all event loop implementations just used the one, true, intended (by Guido) interface for selecting event loop implementations, these kinds of conflicts will be prevented.

from quamash.