New REPL exposes its internal imports/definitions to top-level environment
Open
Nobody has claimed this yet.
3.13
3.14
topic-repl
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
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-119547
- gh-120362
- gh-120370
- gh-120392
- gh-120408
- gh-120430
- gh-121054
- gh-121059
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the _pyrepl.main entry point and reproduce the reported dir() output in the new REPL. Investigate why internal imports and definitions appear in the top-level environment; done means those implementation names are no longer exposed while the REPL still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100