Closed rzhao271 closed 3 years ago
As a note, I can reproduce the issue on Linux (and it seems to work fine on Windows).
I'll investigate.
Ok, I've done some investigation and it seems to be an issue in VSCode itself (I'll report there and link the issue shortly)
Notes:
internalConsole
and with externalTerminal
(so, it only fails with integratedTerminal
).runInTerminal
to the client properly. i.e.: the logs show:D+00000.037: /handling #2 request "launch" from Client[1]/
Client[1] <-- {
"seq": 4,
"type": "request",
"command": "runInTerminal",
"arguments": {
"kind": "integrated",
"title": "Python Debug Console",
"args": [
"/home/fabio/Desktop/miniconda3/envs/py37_tests/bin/python",
"/home/fabio/Desktop/debugpy_workspace/debugpy/src/debugpy/launcher",
"36577",
"--",
"/home/fabio/Desktop/debugpy_workspace/check/test's test/tests's.py"
],
"env": {
"DEBUGPY_LOG_DIR": "/home/fabio/.vscode/extensions/ms-python.python-2021.5.842923320"
},
"cwd": "/home/fabio/Desktop/debugpy_workspace"
}
}
I+00000.024: sys.argv before parsing: ['/home/fabio/Desktop/debugpy_workspace/debugpy/src/debugpy/launcher', '36577', '--', "/home/fabio/Desktop/debugpy_workspace/check/test\\'s test/tests\\'s.py"]
\'
and then wrapping around with "
due to the spaces on the path (which makes the launch fail).So, this appears to be a bug in how VSCode is handling the runInTerminal
(on Linux).
I'm closing the issue here since the issue appears to be on VSCode, not really on debugpy.
Environment data
Version : 1.57.0-insider (user setup) Commit : fe1eafc80c07608de52a2f9c99fee103dea77f5e Date : 2021-06-04T12:21:40.077Z Electron : 12.0.9 Chrome : 89.0.4389.128 Node.js : 14.16.0 V8 : 8.9.255.25-electron.0 OS : Windows_NT x64 10.0.19043
Actual behavior
The file
test's test/hello.py
is not found.Expected behavior
The file
test's test/hello.py
is found.Steps to reproduce:
test's test
.hello.py
with the lineprint('test')
within that directoryhello.py
Also try with the directory test'![](){}|=+-_*&^%$#@!<>,.?~`s test/hello.py