Wrap pythonrc.py logic in a setup()` function to prevent leaking variables
#25651
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR wraps the contents of
pythonrc.pyinside asetup()function to avoid polluting the variables panel of jupyterlab debugger when launched from VS Code and this extension is installed.Context
When JupyterLab is launched from VS Code, the debugger’s Globals panel becomes cluttered with variables injected from the VS Code Python extension’s
pythonrc.py. Examples includeoriginal_ps1,is_wsl,result, and other internal helper variables. These show up as top-level globals in Jupyter kernels, making the debugger view noisy.This change potentially reduces unwanted side effects for external tools (e.g., JupyterLab) while keeping functionality intact.