The chosen python interpreter is not written to workspace's .vscode settings.json file

[rhewy]

Hi,

It would be great if when you choose the python interpreter via the extension the local settings.json file is updated in the .vscode directory. I think it is currently stored in AppData somewhere.

This would make a workspace more portable.

Could also be a setting for the extension to write to the workspace .vscode settings.json file

[eleanorjboyd]

Hi! Yes you are right- what happens right now is the environment manager (ie the type of environment you have like venv or conda) is saved to the settings.json. Then there is internal storage which keeps the interpreter path saved which is controlled by the environment manager. When you say you want the portability, is this when sending others the repo? Since it is common practice not to send it with the venv created already, do you just want the relative path to the venv saved in the settings?

[rhewy]

This could all be related to the separation of the managing of python envs as its own extension.

Then the clarification of roles a responsibilities of each extension: python vs python environments. Who does what?

Even with the following valid settings in AppData\Roaming\Code\User\settings.json

    "python.condaPath": "C:\\apps\\miniconda3\\condabin\\conda.bat",
    "python.defaultInterpreterPath": "C:\\apps\\miniconda3\\envs\\qtui\\python.exe",
    "python.venvPath": "C:\\apps\\miniconda3\\envs",

I still get this even though the default is set:

Then this

However if I interact with the environments extension I have this:

Once I set the environment with the extension this list starts working:

Not much changes in the .vscode/settings.json file and there is no recording of the selection:

{
    "python-envs.defaultEnvManager": "ms-python.python:conda",
    "python-envs.defaultPackageManager": "ms-python.python:conda",
    "python-envs.pythonProjects": []
}

And nothing changes in the AppData\Roaming\Code\User\settings.json

    "python.condaPath": "C:\\apps\\miniconda3\\condabin\\conda.bat",
    "python.defaultInterpreterPath": "C:\\apps\\miniconda3\\envs\\qtui\\python.exe",
    "python.venvPath": "C:\\apps\\miniconda3\\envs",

There are files created in

C:\Users\{usernamr}\AppData\Roaming\Code\User\globalStorage\ms-python.vscode-python-envs\pythonLocator

But the files above are stuck on the local machine and not part of the .vscode folder for the project.

If I start developing on another machine then there is a lot of resetting up every time especially in a VDI environment.

This might get smoothed out over time via the roadmap.

Not sure what the expected behaviour is suppose to be.

[quenching04]

Hi, sorry to bother, I have the same problem too.

• When I only set "python.defaultInterpreterPath": "C:\\Program Files (x86)\\Thonny\\python.exe" in Users setting.json, it works. I can run python code without manually selecting interpreter.

• However, when adding "python.useEnvironmentsExtension": true to Users setting.json, I can't automatically run python in every folder. Instead, I have to choose interpreter, and that creates ".vscode" subfolder in the workspace folder, which contains { "python-envs.defaultEnvManager": "ms-python.python:venv", "python-envs.pythonProjects": [] }

• Then I copy { "python-envs.defaultEnvManager": "ms-python.python:venv", "python-envs.pythonProjects": [] } from workspace folder to Users setting.json, I can still run the code, And there is no ".vscode" subfolder in the workspace folder.

• After using CleanVsCode.bat, when I open the same workspace folder, I need to select the interpreter again. And this time ,the selection action will not create ".vscode" subfolder in the workspace folder.

So the interpreter is stored somewhere else. I wish it would follow what I set in the User settings.json "python.defaultInterpreterPath", so that i can run code without selecting interpreter for every folders.
Or at least be reflected in the ".vscode" subfolder of the workspace folder.

CleanVsCode.txt

[trent-abc]

I don't know if it's a separate issue or not, but I created another issue as a bug report with steps to reproduce:

microsoft/vscode-python#25756

In my case setting python.defaultInterpreterPath in .vscode/settings.json does nothing, the output view/python shows it loading the system python and ignoring the python.defaultInterpreterPath. It would be nice to update the file yes but also nice if the file's values were respected.

If this is supposed to be an issue for this github instead I can re-open one here

[eleanorjboyd]

Hello everyone! Thank you for your comments and use cases here- I am working on this issue right now. I will let you know when a fix is ready for yall to test but we are overhauling how defaultInterpreterPath is respected and the prioritization of these settings. It will look something like this going foward:

How the Extension Chooses Your Interpreter

When you open a workspace, the extension checks these settings in order. The first one that applies wins:

1. python-envs.pythonProjects[]      →  Project-specific configuration (highest priority)
2. python-envs.defaultEnvManager     →  Your preferred environment manager
3. python.defaultInterpreterPath     →  Specific Python executable path
4. Auto-discovery                    →  Finds .venv folders or system Python (lowest priority)

Note: A setting you never configured won't override one you did configure, even if the unconfigured setting has higher priority. For example, if you set python.defaultInterpreterPath but never touched python-envs.defaultEnvManager, your interpreter path will be used.