Avoid leaking variables in PyREPL #26147

Activity

1. github-actions

   added

   triage-neededNeeds assignment to the proper sub-teamNeeds assignment to the proper sub-team

   on Sep 10, 2026
2. Eduardo Villalpando Mello (edvilme)

   closed this as completedin #26148on Sep 10, 2026
3. vs-code-engineering commented on Sep 10, 2026

   

   vs-code-engineeringbot

   on Sep 10, 2026 – with VS Code Engineering

   More actions

   Sharing media and context from merged PR #26148 for verification:

   Before

   

   After

   

   This pull request refactors the initialization logic in python_files/pythonrc.py to avoid polluting the module's global namespace, and adds a corresponding test to ensure this behavior. The main change is wrapping the script's setup code in a private function and then deleting it after execution.

   Refactoring and namespace cleanliness:

   • Moved all initialization code in pythonrc.py into a private _initialize() function, and called and deleted it at the end of the file to prevent leftover names in the module's global namespace. [1] [2]
   • Removed unnecessary blank lines and improved code organization for readability. [1] [2] [3]

   Testing:

   • Added test_does_not_pollute_namespace in test_shell_integration.py to verify that pythonrc.py does not leave any non-dunder (non-__) names in its global namespace after import.

   Source PR: #26148
4. pull

   added a commit that references this issue on Sep 10, 2026

   Pythonrc: Don't pollute PyREPL with variables (microsoft#26148)

   ...

   This issue will close once commit cb7b164 is merged into the 'main' branch.

   cb7b164
5. Eduardo Villalpando Mello (edvilme)

   marked Avoid loading sys and platform modules into namespace when running PYTHONSTARTUP in integrated terminal #25904 as a duplicate of this issue on Sep 10, 2026