-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python File debugger fails due to triple quotes in command line #5861
Comments
Ran into this issue today, so downgraded the extension to version |
@xyx0826, thanks for letting us know about this. I have a few questions:
Ultimately a simple set of steps to reproduce the problem on our end would help a lot. |
@ericsnowcurrently, Thanks for your reply. No I don't believe the quotes are unique to my environment, except for the fact that I have spaces in my username. I will update after I test with a path without spaces. In fact I don't have a Yes, this issue started to appear recently (within a week?) Thanks. |
@DonJayamanne, any thoughts on where those extra quotation marks are coming from? |
@ericsnowcurrently providing some info that might help |
|
@xyx0826 |
@DonJayamanne, yes I do. Sorry I wasn't able to find a time to test it out with a space-free path. |
I had the exact same issue and I do have a space in my name. On occasion, it presents issues with some Python packages, but it is rare. Instead of renaming all my PATHs I downgraded the Extention to 2019.4.12954 and everything worked fine. I presume that it all started when I first upgraded to 2019.5.x. |
Yes, we'll be resolving this soon. Apologies for the inconvenience caused. |
Issue was resolved in |
@BaluPraveen Thanks for the confirmation. |
Environment data
1.34.0 (user setup)
a622c65b2c713c890fcf4fbf07cf34049d5fe7582019.6.17655-dev
Windows_NT x64 10.0.18898
v3.7.3:ef4ec6ed12
w/pip
venv
None
Expected behaviour
The Python File debugging configuration is able to run the current Python file under the debugger.
Actual behaviour
Triple quotes in the debugger bootstrap command leads to an error.
Steps to reproduce:
Debug > Start Debug > Python File
to start the current file under debugger.(Reproductible with Python 2.7 and non-venv Python 3)
4. The following error will be displayed:
(Note the triple quotes have been replaced by single quotes)
6. The
debuggerdebuggee successfully starts and connects to VSCode, debugging begins.Logs
Output from
Console
under theDeveloper Tools
panel: https://gist.github.com/xyx0826/ef472d164cc5e7265f361fd70234e72fThe text was updated successfully, but these errors were encountered: