758719 – sys-apps/portage: [TRACKER] use default asyncio event loop implementation in threads and child processes

Bug 758719 - sys-apps/portage: [TRACKER] use default asyncio event loop implementation in threads and child processes

Summary: sys-apps/portage: [TRACKER] use default asyncio event loop implementation in ...

Status:	CONFIRMED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Core (show other bugs)
Hardware:	All All

Importance:	Normal normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:	Tracker

Depends on:	761538 591760 758740 758755 764905
Blocks:
	Show dependency tree

Reported:	2020-12-06 07:08 UTC by Zac Medico
Modified:	2021-01-11 06:03 UTC (History)
CC List:	0 users

See Also:	737698
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Zac Medico gentoo-dev

2020-12-06 07:08:57 UTC

Currently portage uses its internal EventLoop implementation in threads and child processes. It would be better if the default asyncio event loop implementation could be used instead, in order to support new features such as PEP 525 asynchronous generators. For forks, hopefully https://bugs.python.org/issue22087 can suppressed  by instantiating a new event loop in the subprocess, which is supported since https://bugs.python.org/issue29703 was fixed.