Bug report

Bug description:

This is an issue for a pre-existing PR#140298.

The problem lies in:

(I wrote this 😬)

It resorts tospawn_repl that adds-i on top of-m asyncio:

Mixing-i with-m asyncio causes the asyncio REPL to launch first, and then a regular Python REPL--right after the former exits.
This is an expected outcome when-i and-m asyncio are mixed.
I didn't intend this result of the current setup--we want-i^<custom repl args> to run a REPL when testing without a PTY.

CPython versions tested on:

3.15

Operating systems tested on:

Linux

Linked PRs

• gh-140438: Properly run the asyncio REPL in REPL tests #140298
• [3.14] gh-140438: properly run the asyncio REPL tests (GH-140298) #140507
• [3.13] gh-140438: properly run the asyncio REPL tests (GH-140298) #140508