$PATH ordering is wrong when running with Python debugger.

[tbenthompson]

Issue Type: Bug

1. Open a Python file.
2. Press Ctrl-F5 to run a Python file.
3. The Python file uses another executable (specifically, clang).
4. My code fails because the $PATH order is different than it should be and as a result the clang call is using the wrong clang installation and fails..

See the screenshots for how the which clang output differs between the debugger terminal and the standard terminal. The origin of this problem is that the $PATH environment variable is in the wrong order in the debugger terminal.

Extension version: 2022.4.1
VS Code version: Code 1.66.2 (Universal) (dfd34e8260c270da74b5c2d86d61aee4b6d56977, 2022-04-11T07:49:20.994Z)
OS version: Darwin arm64 21.4.0
Restricted Mode: No

System Info

Item	Value
CPUs	Apple M1 Max (10 x 24)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled metal: disabled_off multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled
Load (avg)	5, 4, 3
Memory (System)	64.00GB (23.60GB free)
Process Argv	--crash-reporter-id b532f079-f941-47c0-ab2f-f74d9a137557
Screen Reader	no
VM	0%

[karrtikr]

Please try changing the setting terminal.integrated.inheritEnv to false as outlined in https://code.visualstudio.com/updates/v1_36#_launch-terminals-with-clean-environments and see if it helps.

[paulacamargo25]

Thanks for the bug report, could you please share your launch.json configuration?

[tbenthompson]

So, if terminal.integrated.inheritEnv is false, then I see the $PATH:

/Users/tbent/.mambaforge/envs/kevlar/bin:/Users/tbent/.mambaforge/condabin:/opt/homebrew/bin:/Users/tbent/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin:/Library/Apple/usr/bin

which corresponds to the second example above. If terminal.integrated.inheritEnv is true, then I see the $PATH:

/opt/homebrew/bin:/Users/tbent/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin:/Library/Apple/usr/bin:/Users/tbent/.mambaforge/envs/kevlar/bin:/Users/tbent/.mambaforge/condabin:/opt/homebrew/bin:/Users/tbent/bin

which corresponds to the first example above.

So, to summarize, it appears that the shell environment used for running a Python script via ctrl-F5 is the shell environment produced by inheritEnv being true, even though I have that setting set to false.

So, perhaps another way of stating the bug here is to say that launching Python this way is ignoring the inheritEnv setting.

This is my launch.json:

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python: Current File",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal",
            "justMyCode": true
        }
    ]
}