'terminal.integrated.shell.windows' of workspace is ignored by python launcher

Environment data

• VS Code version: 1.44.0
• Extension version (available under the Extensions sidebar): 2020.3.71659
• OS and version: Windows 10 ver.1909
• Python version (& distribution if applicable, e.g. Anaconda): 3.7.7
• Type of virtual environment used (N/A | venv | virtualenv | conda | …): venv
• Relevant/affected Python packages and their versions: (None)
• Relevant/affected Python-related VS Code extensions and their versions: (None)
• Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): True
• Value of the python.languageServer setting: Microsoft

Expected behaviour

If ‘terminal.integrated.shell.windows’ is set in XXX.code-workspace file, it overrides the same value of user level setting.

Actual behaviour

Python launches on ‘terminal.integrated.shell.windows’ of user setting, and it ignores ‘terminal.integrated.shell.windows’ of workspace setting.

Steps to reproduce:

1. Set workspace Create test.code-workspace as the following;

{
	"folders": [
		{
			"path": "."
		}
	],
	"settings": {
		"terminal.integrated.shell.windows": "${env:SystemRoot}\\system32\\cmd.exe"
	}
}

1. Open this workspace from menu [Open Workspace]

2. Open terminal (i.e. [Ctrl]+[j])

Command Prompt is opened.

Select [Allow], if VSC shows the message about ‘Terminal change’.

1. Change default terminal to PowerShell in terminal menu ‘Select Default Shell’

2. Open terminal again (i.e. [+] button of terminal window top)

Command Prompt is opened.

1. Open python code on editor and start debug (i.e. [F5])

Python launches on PowerShell

[ImpulseAdventure]

@Hoshino-Roxy – for future reference & for others also encountering your issue:

• The workspace-scoped override of the terminal.integrated.shell settings are disabled by default in vscode.
• You can enable this from View -> Command Palette and selecting “Terminal: Manage Workspace Shell Permissions”.

[ericsnowcurrently]

I’m not seeing anything useful in the extension’s logs. As noted earlier, you’ll need to open a new issue against VS Code. Sorry we couldn’t help.