forked from DonJayamanne/pythonVSCode
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Labels
area-environmentsFeatures relating to handling interpreter environmentsFeatures relating to handling interpreter environmentsdebtCovers everything internal: CI, testing, refactoring of the codebase, etc.Covers everything internal: CI, testing, refactoring of the codebase, etc.
Description
Related: #24122
We may be selecting undesired conda environment in
vscode-python/src/client/common/process/pythonExecutionFactory.ts
Lines 130 to 135 in c314bab
const condaExecutionService = await this.createCondaExecutionService(pythonPath, processService); | |
if (condaExecutionService) { | |
return condaExecutionService; | |
} | |
const env = createPythonEnv(pythonPath, processService, this.fileSystem); | |
return createPythonService(processService, env); |
- Noted on the referenced PR Allow pytest to use correct interpreter from getActiveInterpreter #24233 but the culprit may be that we were not passing in interpreter information for discovery, execution of testing as a option.
TODO:
- Investigate how pythonexecutionFactory is related to Select interpreter dropdown we have. => These two are separate things.
- Ensure these two Python environment/executables are aligned.
- Potentially look into some environment service where we can store the state of currently selected environment.
/cc @eleanorjboyd
eleanorjboyd
Metadata
Metadata
Assignees
Labels
area-environmentsFeatures relating to handling interpreter environmentsFeatures relating to handling interpreter environmentsdebtCovers everything internal: CI, testing, refactoring of the codebase, etc.Covers everything internal: CI, testing, refactoring of the codebase, etc.