Activity

1. github-actions

   added

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

   on Nov 5, 2026
2. vs-code-engineering

   assigned

   Anthony Kim (anthonykim1)

   on Nov 5, 2026
3. vs-code-engineering

   removed

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

   on Nov 5, 2026
4. akoronn commented on Nov 9, 2026

   

   akoronn (akoronn)

   on Nov 9, 2026

   More actions

   Bug: "Run Python File" passes literal quotation marks in the script path on Windows PowerShell

   Description

   When using the Run Python File command in VS Code, extra double quotation marks are included in the script path passed to Python.

   As a result, Python cannot locate the script and exits with an Invalid argument error.

   This issue started occurring after a recent VS Code update. The same workflow worked correctly before the update.

   Steps to Reproduce

   1. Open a Python project in VS Code.
   2. Use a project directory whose path contains spaces and non-ASCII characters (Japanese characters in my case).
   3. Create and activate a virtual environment.
   4. Open a Python file.
   5. Click Run Python File.

   Actual Behavior

   VS Code generates the following command:

   & '<project-path>\.venv\Scripts\python.exe' '"<project-path>/gui.py"'

   Notice that the script path contains an additional pair of double quotation marks inside the single-quoted PowerShell argument.

   Python interprets these double quotation marks as part of the filename and fails to open the script.

   Error message:

   python.exe: can't open file '<project-path>\"<project-path>\gui.py"': [Errno 22] Invalid argument
   

   Expected Behavior

   The command should pass the script path without the extra literal double quotation marks:

   & '<project-path>\.venv\Scripts\python.exe' '<project-path>/gui.py'

   The script should execute normally.

   Additional Information

   • The issue occurs only when using Run Python File.
   • Running the same script through the VS Code debugger (F5) works correctly.
   • Running the script manually with a correctly quoted command also works.
   • The virtual environment is activated successfully.
   • The project path contains both spaces and Japanese characters.
   • This issue did not occur before a recent VS Code update.

   This suggests that the issue is related to command generation or argument quoting in the Python extension's terminal execution path.

   Environment

   Operating System

   • Windows 11
   • Windows_NT x64 10.0.26300
   • PowerShell

   VS Code

   • Version: 1.145.2 (User Setup)
   • Commit: c4453f8ea430795f941c1b2ff6c9321135a74a02
   • Date: 2026-11-06T04:28:13Z
   • Electron: 43.8.3
   • Chromium: 150.0.7871.250
   • Node.js: 24.22.1
   • V8: 15.0.245.31-electron.0

   Python

   • Version: 3.14.8
   • Interpreter: .venv\Scripts\python.exe

   Extensions

   • Python (ms-python.python): 2026.10.0
   • Python Debugger (ms-python.debugpy): 2026.7.13061010
   • Python Environments (ms-python.vscode-python-envs): 1.43.2026110501
   • Pylance (ms-python.vscode-pylance): 2026.4.1