New REPL exposes its internal imports/definitions to top-level environment

[chgnrdv]

Bug report

Bug description:

Top-level scope now contains globals of _pyrepl.__main__:

Python 3.14.0a0 (heads/main:a895756aec, May 10 2024, 16:56:55) [GCC 10.2.1 20210110] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> dir()
['CAN_USE_PYREPL', '__annotations__', '__builtins__', '__cached__', '__doc__', '__file__',
'__loader__', '__name__', '__package__', '__spec__', 'interactive_console', 'os', 'sys']

CPython versions tested on:

3.13

Operating systems tested on:

Linux

Linked PRs

• gh-118908: Limit exposed globals from internal imports and definitions on new REPL startup #119547
• [3.13] gh-118908: Limit exposed globals from internal imports and definitions on new REPL startup (GH-119547) #120362
• gh-118908: Fix completions after namespace change in REPL #120370
• [3.13] gh-118908: Fix completions after namespace change in REPL (GH-120370) #120392
• gh-118908: Protect the REPL subprocess with a timeout in tests #120408
• [3.13] gh-118908: Protect the REPL subprocess with a timeout in tests (GH-120408) #120430
• gh-118908: Use __main__ for the default PyREPL namespace #121054
• [3.13] gh-118908: Use __main__ for the default PyREPL namespace (GH-121054) #121059

[encukou]

It seems that this change broke a buildbot, see: https://buildbot.python.org/all/#/builders/249/builds/8895/steps/5/logs/stdio

[pablogsal]

It seems that this change broke a buildbot, see: https://buildbot.python.org/all/#/builders/249/builds/8895/steps/5/logs/stdio

It looks like a timeout.... I will try to investigate today

[lysnikolaou]

The timeout should be fixed now.

[ambv]

The fix is invalid. It makes it impossible to auto-import stuff with PYTHONSTARTUP.