Python-specific remote settings is ignored

[jhrmnn]

I wasn't able to submit the Issue from VS Code, "Create on Github" in the Issue Reporter would do nothing.

Behaviour

Expected vs. Actual

Remote settings in the [python] section should be applied to Python files but it is ignored with v2024.4.0. Downgrading to v2024.2.1 resolves this issue. Upgrading back to v2024.4.0 then retains the correct behavior.

Steps to reproduce:

1. Launch VS Code in a dev container or for a Github Codespace that specifies a Python-specific VS code settings (customizations.vscode.settings.[python])
2. Observe that the settings is not applied.

Diagnostic data

• Python version (& distribution if applicable, e.g. Anaconda): 3.10.14
• Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Conda
• Value of the python.languageServer setting: Default

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

User Settings

languageServer: "Pylance"

testing
• pytestArgs: "<placeholder>"
• pytestEnabled: true

[jhrmnn]

Just found out it's not necessary to downgrade the extension, it's sufficient to simply reload the VS Code window (Developer: Reload Window).

[karthiknadig]

Did you reload after installing 2024.4.0 ? or was this reload with a different version?

Python extension does not do anything special here, all we do is rely on VS code to read setting. It is likely that the dev-container settings are not seen by vscode.

[jhrmnn]

The reload was with the latest version, 2024.4.0. So I found only after posting the original Issue that downgrading is not necessary, all the the downgrade did was forcing me to reload, and it’s the reload itself that resolves the issue. Which is, of course, inconvenient.

So to state it again, the remote Python-specific settings is not seen by vscode (filtering settings for @lang:python @modifed gives nothing), and after “Developer: Reload Window”, it is seen.

I don’t remember this being the case some time ago, but of course other things than the Python extension might have changed. Will try to find the root cause. Any tips what to look for?

[jhrmnn]

Should I then likely re-file the Issue with VS Code core then?

[jhrmnn]

Just confirmed that the same thing happens when the Codespace is launched in browser on github.dev instead of in VS Code. As in, on first load the Python-specific settings is ignored and on browser reload it is respected.

[karthiknadig]

Moving this to VS Code as this is related to the settings.