Re: [PATCH] Use default asyncio event loop implementation in API consumer threads
Zac Medico <[email protected]> Sun, 6 Dec 2020 03:38:41 -0800
| Newsgroups | gmane.linux.gentoo.portage.devel |
|---|---|
| Message-ID | <[email protected]> |
On 12/6/20 1:46 AM, Zac Medico wrote: > Make the _safe_loop function an alias for the global_event_loop > function, so that the default asyncio event loop implementation > will be used in API consumer threads. This is possible because > global_event_loop has been fixed (bug 758740) to always use > AsyncioEventLoop, and that uses asyncio.get_event_loop() which > returns a new event loop for each thread. I think we may still need a separate _safe_loop function here, since global_event_loop returns a separate loop per pid, but _safe_loop needs to return a separate loop per thread. -- Thanks, Zac
signature.asc
(application/pgp-signature, 981 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQKTBAEBCgB9FiEE8OgXaltWzqgSupCu0HX7jBBKPSAFAl/MwsFfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEYw RTgxNzZBNUI1NkNFQTgxMkJBOTBBRUQwNzVGQjhDMTA0QTNEMjAACgkQ0HX7jBBK PSB30xAAsAagL79a9MF9EOhMmYT8twfS5sfp0Sni4wqcyTL1sXUjzyAIXnq1s4P+ MZ8jtrmm9qEguYQN7QgOuIm8paP/FVpXUhpTSqNm7PylxHTDz1WiTJ9ydAdEl5CR RFtko+X/Rik+EFo3qhAYJ+3vRkkZPtgSqwEbMgpcAYyiVgmvECFgistujQpJ7yzT h3LbdZN1tOxSBNZ2oK8E4OyegK6LrddbC0Ou2hRPrVnIgVAiX7tdTEzpyhnppZgK ll7OKvphgIOiDKZo+jPRCe8fLIS368j4mydIICADbdJkyvHlZt4oxAzf00dBhUF2 XhFpn202m1jBycsBVFleI2cff4N/ozumSz9dxj3rmLYzWOHm4x/zhQpsIJJoiJZE mSYc0yrFtTxNbiCOL9q8gu9NS4QS9+gqDeBcPmuCsWxLUForml/sZSXpAZ05SKvy iCjnfz+BkXnhNTq8EfsgVNAqCkoEmeer239KJCPrufBquzqVjiJNgZrGTiOmeKPp PW/x/tCmm4BsivqSQi28lcEndI/wHnToZVcDcXOlWmHhVupH2zpbzQEbu+0nSgTQ 6wyHXKS+eXkvMaoZtOUIlvXuTvGj+JHxS/cLNo8mQh1FWtNLDoA2I1MYOyHJFynu 8BEMdExRsjDXxw8mPSENaaOxzMhXotv0YVaSYwwKC7fx6fixjSs= =v+Il -----END PGP SIGNATURE-----