I can't run or debug in a path that contains white spaces with a venv

[juanfcocontreras]

Type: Bug

Behaviour

I can't run or debug in a path with a virtual environment that contains white spaces with the update of both VSCode and Python released today. If I move the same project to a path without spaces, it works without any issues.

Steps to reproduce:

1. Create a Python project
2. Create a virtual environment
3. Select the virtual environment as the interpreter
4. Run the main program

I have verified that the file reported as non-existent in the output console ("/code/embedding test/.venv/bin/python") does exist in the file system.

Diagnostic data

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

[warning] Failed to check if "/code/embedding test/.venv/bin/python" is an executable [Error: ENOENT: no such file or directory, lstat '"/code/embedding test/.venv/bin/python"'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'lstat',
  path: '"/code/embedding test/.venv/bin/python"'
}

Extension version: 2025.16.0
VS Code version: Code 1.105.0 (03c265b1adee71ac88f833e065f7bb956b60550a, 2025-10-08T14:09:35.891Z)
OS version: Darwin arm64 25.0.0
Modes:

• Python version (& distribution if applicable, e.g. Anaconda): 3.12.11
• Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Venv
• Value of the python.languageServer setting: Pylance

User Settings

languageServer: "Pylance"

experiments
• optInto: ["All"]

Installed Extensions

Extension Name	Extension Id	Version
austin-vscode	p40	0.17.3
autodocstring	njp	0.6.1
camouflage	zey	1.1.1
commands	use	1.16.0
continue	Con	1.2.8
datawrangler	ms-	1.22.0
debugpy	ms-	2025.14.0
djlint	mon	2025.9.0
errorlens	use	3.26.0
even-better-toml	tam	0.21.2
file-properties-viewer	bru	1.2.0
git-autoconfig	shy	0.0.2
git-graph	mhu	1.30.0
gitignore	cod	0.10.0
gitpatch	par	0.2.1
gremlins	nho	0.26.0
icons	tal	3.8.0
indent-rainbow	ode	8.3.1
jinjahtml	sam	0.20.0
js-debug	ms-	1.105.0
js-debug-companion	ms-	1.1.3
jupyter	ms-	2025.9.0
jupyter-keymap	ms-	1.1.2
jupyter-renderers	ms-	1.3.0
juxtacode	Yor	1.1.1
live-server	ms-	0.4.16
nicegui	Dae	0.9.6
numbermonger	sof	0.5.0
open-in-browser	tec	2.0.0
path-intellisense	chr	2.10.0
pdf	tom	1.2.2
project-tree	zhu	0.4.0
python	ms-	2025.16.0
quarto	qua	1.126.0
rainbow-csv	mec	3.23.0
remote-containers	ms-	0.427.0
remote-explorer	ms-	0.5.0
remote-ssh	ms-	0.120.0
remote-ssh-edit	ms-	0.87.0
replacerules	bhu	0.4.2
resourcemonitor	mut	1.0.7
ruff	cha	2025.28.0
shiny	Pos	1.3.1
text-power-tools	qcz	1.51.0
theme-dark-plus-contrast	k3a	1.76.0
uv-toolkit	the	0.1.7
vscode-commons	red	0.0.6
vscode-dash	dee	2.4.0
vscode-django	bat	1.15.0
vscode-dotnet-runtime	ms-	2.3.7
vscode-js-profile-table	ms-	1.0.10
vscode-jupyter-cell-tags	ms-	0.1.9
vscode-jupyter-slideshow	ms-	0.1.6
vscode-map-preview	jum	0.7.0
vscode-open	san	0.3.0
vscode-pylance	ms-	2025.8.3
vscode-readme	thr	0.0.2
vscode-todo-plus	fab	4.19.1
vscode-xml	red	0.29.0
vscode-yaml	red	1.19.1

System Info

Item	Value
CPUs	Apple M3 (8 x 2400)
GPU Status	2d_canvas: enabled direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: enabled_on trees_in_viz: disabled_off video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	7, 6, 5
Memory (System)	24.00GB (2.38GB free)
Process Argv
Screen Reader	no
VM	0%

[PIrojahPerbak]

Can confirm this is an ongoing issue for me too

[Ijsschreeuw]

Also having this issue.

[aotto61]

VSC updated an hour ago. Now it won't debug. It redirects me to the launch.json file, which I updated with 'tipe = debugpy'. But debugging always stops immediately. I installed Python version 13.13.1 on Windows 10 Home 22H2.

[juanfcocontreras]

VSC updated an hour ago. Now it won't debug. It redirects me to the launch.json file, which I updated with 'tipe = debugpy'. But debugging always stops immediately. I installed Python version 13.13.1 on Windows 10 Home 22H2.

The problem is with the Python Debugger extension. They have already fixed it in a new version of Python Debugger extension (that's why this issue is closed); we just have to wait for it to arrive in the Marketplace.

microsoft/vscode-python-debugger#828 (comment)