Bug report

Bug description:

Most importantly, it doesn't call.close() on it, which blocksGH-140288 and causes surprising warnings on Windows (seeGH-141262).

Ideally, we'd employasyncio.Runner to manage the tricky and ever-changing parts of the lifecycle pipeline correctly.

CC@ZeroIntensitystdlib,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

• gh-142784: Make the asyncio REPL call.close() on the loop #142785
• [3.13] gh-142784: make the asyncio REPL callloop.close() at exit (GH-142785) #142932
• [3.14] gh-142784: make the asyncio REPL callloop.close() at exit (GH-142785) #142933