Bug report
Bug description:
Most importantly, it doesn't call .close() on it, which blocks GH-140288 and causes surprising warnings on Windows (see GH-141262).
Ideally, we'd employ asyncio.Runner to manage the tricky and ever-changing parts of the lifecycle pipeline correctly.
CC @ZeroIntensity stdlib, topic-repl, topic-asyncio, 3.13, 3.14, 3.15
CPython versions tested on:
CPython main branch, 3.15, 3.14, 3.13
Operating systems tested on:
Linux, Windows, macOS
Linked PRs
Bug report
Bug description:
Most importantly, it doesn't call
.close()on it, which blocks GH-140288 and causes surprising warnings on Windows (see GH-141262).Ideally, we'd employ
asyncio.Runnerto manage the tricky and ever-changing parts of the lifecycle pipeline correctly.CC @ZeroIntensity
stdlib,topic-repl,topic-asyncio,3.13,3.14,3.15CPython versions tested on:
CPython main branch, 3.15, 3.14, 3.13
Operating systems tested on:
Linux, Windows, macOS
Linked PRs
.close()on the loop #142785loop.close()at exit (GH-142785) #142932loop.close()at exit (GH-142785) #142933