python debugging script will not now use command as terminal. It opens a pwershell terminal instead.

[pbs-websuntangled]

Issue Type: Bug

It was working fine until vscode restarted and updated to the August 2021 edition.

From that point debug would only open a pwershell terminal

The default terminal was also changed to powershell

I reverted that back to command termional and now opening a new terminal works as expected

But debug still only opens pwershell terminal

I downgraded to July 2021 version and that now behaves in the same problematic way (debugging python only opens in powershell)

I cannot start using powershell terminals because I use anaconda to manage python environments and powershell refuses to activate anaconda environments

VS Code version: Code 1.60.0 (e7d7e9a, 2021-09-01T10:41:52.311Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

System Info

Item	Value
CPUs	AMD Ryzen Threadripper 1950X 16-Core Processor (32 x 3394)
GPU Status	2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled skia_renderer: enabled_on video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	31.88GB (18.43GB free)
Process Argv	--crash-reporter-id 62687609-2214-4260-a68c-e81d20dfa052
Screen Reader	no
VM	0%

Extensions (11)

Extension	Author (truncated)	Version
githistory	don	0.6.18
python	ms-	2021.9.1191016588
vscode-pylance	ms-	2021.9.0
jupyter	ms-	2021.8.2031190714
jupyter-keymap	ms-	1.0.0
cpptools	ms-	1.6.0
vscode-commons	red	0.0.6
vscode-yaml	red	0.22.0
LiveServer	rit	5.6.1
vscode-3dviewer	sle	0.2.2
vscode-arduino	vsc	0.4.4

A/B Experiments

vsliv368:30146709
vsreu685:30147344
python383cf:30185419
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
pythonvspyt639:30300192
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
pythonvsuse255:30340121
vscod805cf:30301675
pythonvspyt200:30340761
vscextlang:30333561
binariesv615:30325510
pythonvssor306:30344512
bridge0708:30335490
pygetstartedt2:30360495
bridge0723:30353136
pythonf5test824:30361777
vsdyn321cf:30356811
pythonvspyt187cf:30361754
pydsgst2:30361792
vscus224cf:30358040
vssid140cf:30362081

[gjsjohnmurray]

Probably the same root cause as #132149

I'm guessing there'll be a recovery build to fix this.

[ssoworld]

If you kill the terminal, then do ctrl+`, it will load your desired default

[Duoquote]

Same issue here, in my config:

{
  ...
  "terminal.integrated.defaultProfile.windows": "Command Prompt",
  ...
}

It is defined as Command Prompt and opening a terminal works just fine but when I try to run my django launch configuration with conda environment:

{
      "name": "Django: Server",
      "type": "python",
      "request": "launch",
      "program": "${workspaceFolder}/location-getty-server/manage.py",
      "args": [
        "runserver"
      ],
      "django": true
}

It's unable to activate conda environment because of powershell path things:

So I am fully unable to use debug mode, also been trying to get conda working with powershell for the last 3-4 hours... Wondering how long will that issue last.

[meganrogge]

/duplicate #132150