-
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
${workspaceFolder} variable not working #258
Comments
@thernstig Out of curiosity, why are you changing it to workspaceFolder? |
@DonJayamanne workspaceRoot is being deprecated to make it consistent with multi-root workspace support. This was mentioned in version 1.17: https://code.visualstudio.com/updates/v1_17#_workspacefolder-in-launchjson-and-tasksjson It was further elaborated upon in version 1.18: https://code.visualstudio.com/updates/v1_18#_workspacefolder-replaces-workspaceroot (congrats on the new job!) |
@thernstig somehow I missed the new name. Thanks |
Fixes #258 * use workspaceFolder token instead of workspaceRoot * fix typo * updated to properly describe intent of test
Environment data
VS Code version: 1.18.1
Python Extension version: 0.8.0 (9 November 2017)
Python Version: 3.6.1
OS and version: Windows 10 Home, Version 1703, OS-version 15063.483
Actual behavior
In the settings, when changing
"python.pythonPath": "${workspaceRoot}/venv/Scripts/python.exe",
to"python.pythonPath": "${workspaceFolder}/venv/Scripts/python.exe",
the venv will stop working.The status bar says "Select Python Environment", indicating it could not find the virtual environment.
Expected behavior
It is expected that the virtual environment is found. The status bar should say something similar to:
Steps to reproduce:
The text was updated successfully, but these errors were encountered: