-
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
Not able to run or debug #3452
Comments
What is This is not being reported by anyone else so this very likely is due to something unique on your system. |
And what does |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@glutanimate I don't think we ever officially supported it (I believe we do support |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
FYI I am waiting to hear back from @ivannp about his settings. Everyone else asking for some |
@brettcanjon |
Duplicate of #3392 |
Hi Brett, Here is the output:
I am using the def environment both from command line and from Visual Studio. It's unlikely that there is any issue with it. Also have tried different settings for python.pythonPath. Here is what I currently have in settings.json which shows in vscode:
When I run it, I get:
In addition, I removed other python.exe from the path - no success. Where is vscode loading the interpreter from? Are there any other places that it might be looking? |
@brettcannon FYI the support of {env:...} was working on previous releases. That's what I meant in my report. |
Environment data
Actual behavior
Trying to debug or run a file loaded in vscode always tells me that I need to select an interpreter. After I do that, see the image below confirming that an interpreter is set:
I keep getting:
Expected behavior
Being able to run the file with the selected interpreter
The text was updated successfully, but these errors were encountered: