-
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 does not respect Workspace path / environment variable shortcuts. #7684
Comments
Thanks for reporting this issue. |
@DonJayamanne Any suggestion on where this issue might be? |
Nope, we'll need to test this locally. |
This is another regression in the environment variable resolution. |
I have similar issue with |
Have we managed this replicate this issue? |
Does not happen for me in the latest release of the extension. Please open a new issue if it still happens. |
The Python extension for VS Code does not respect VS Code's path variables for setting the Python interpreter path.
Environment data
"python.jediEnabled"
set to; more info How to update the language server to the latest stable version #3977): Language ServerExpected behaviour
Setting a custom Python interpreter path in a VS Code workspace file with "python.pythonPath" should respect VS Code path shortcuts so, e.g. this should work:
"python.pythonPath": "${env:PROGRAMFILES}/blender foundation/blender/2.80/python/bin/python.exe",
Actual behaviour
The environment variable shortcut is not recognized so the custom Python interpreter is not recognized. to get it to work the environment variable shortcut must be expanded out absolutely:
"python.pythonPath": "c:/program files/blender foundation/blender/2.80/python/bin/python.exe",
Steps to reproduce:
Logs
Output for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)Output from
Console
under theDeveloper Tools
panel (toggle Developer Tools on underHelp
; turn on source maps to make any tracebacks be useful by runningEnable source map support for extension debugging
)The text was updated successfully, but these errors were encountered: