Context
When running the Python language server backed by Jedi, I've found that selecting a different Python interpreter from a different environment doesn't yield any code completions.
However, if I were to run the following commands before launching VSCode:
$ conda activate custom_env
$ code
then custom_env's Python interpreter would be picked up successfully.
Proposal
As proposed in #22466, we could look to leverage environmentPath (ref) in the analysis options to avoid the current behaviour where Jedi would simply fallback to the default activated environment.
Context
When running the Python language server backed by Jedi, I've found that selecting a different Python interpreter from a different environment doesn't yield any code completions.
However, if I were to run the following commands before launching VSCode:
then custom_env's Python interpreter would be picked up successfully.
Proposal
As proposed in #22466, we could look to leverage
environmentPath(ref) in the analysis options to avoid the current behaviour where Jedi would simply fallback to the default activated environment.