Repository navigation
The asyncio REPL does not manage the event loop properly #142784
Description
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
Activity
kumaraditya303 commentedon Dec 17, 2025
I think the simpler change is to just call
loop.close,asyncio.Runnerfeels overkill for this.johnslavik commentedon Dec 18, 2025
Sure. If we ever need a runner, we can add it later. 👍
gh-142784: make the asyncio REPL call `loop.close()` at exit (#142785)
pythongh-142784: make the asyncio REPL call `loop.close()` at exit (p…
pythongh-142784: make the asyncio REPL call `loop.close()` at exit (p…
[3.14] gh-142784: make the asyncio REPL call `loop.close()` at exit (G…
[3.13] gh-142784: make the asyncio REPL call `loop.close()` at exit (G…
pythongh-142784: make the asyncio REPL call `loop.close()` at exit (p…