Resolve system variables in the defaultInterpreterPath entry #18351

Activity

1. Kim-Adeline Miguel (kimadeline)

   added

   bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug

   needs PR

   area-environmentsFeatures relating to handling interpreter environmentsFeatures relating to handling interpreter environments

   verification-neededVerification of issue is requestedVerification of issue is requested

   on Jan 24, 2022
2. Kim-Adeline Miguel (kimadeline)

   added this to the January 2022 milestone on Jan 24, 2022
3. Kim-Adeline Miguel (kimadeline)

   self-assigned this

   on Jan 24, 2022
4. Kim-Adeline Miguel (kimadeline)

   closed this as completedon Jan 24, 2022
5. kimadeline commented on Jan 25, 2022

   

   Kim-Adeline Miguel (kimadeline)

   on Jan 25, 2022

   Last edited by kimadeline

   Author

   More actions

   Repro steps:

   • Have a workspace with Python files and a .code-workspace file
   • Create a subfolder in the workspace, and then create a virtual environment in that subfolder (any flavor of Python 3 works): cd subfolder; python3 -m venv .venv
   • Add the following to the .code-workspace file:

   {
       "settings": {
           "python.defaultInterpreterPath": "${workspaceFolder}/path/to/python.exe",
       }
   }

   On windows the path to the python executable will be something like ${workspaceFolder}/<folder>/.venv/Scripts/python.exe, while on Unix it will be ${workspaceFolder}/<folder>/.venv/bin/python.exe

   • Open the workspace and activate the extension
   • Run the Select Interpreter command, and verify that the path in the Use Python from 'python.defaultInterpreterPath' setting entry is a valid path that contains no system variables
   • Select that entry, and verify that it is a usable Python interpreter (the extension works, and operations like linting or formatting work)
6. Rich Chiodo (rchiodo)

   added

   verifiedVerification succeededVerification succeeded

   on Jan 26, 2022
7. rchiodo commented on Jan 26, 2022

   

   Rich Chiodo (rchiodo)

   on Jan 26, 2022

   More actions

   /verified
8. github-actions

   locked as resolved and limited conversation to collaborators on Feb 26, 2022