command python.xxx not found in workspaces without folders

Environment data

• VS Code version: 1.28.1-1539281690
• Extension version (available under the Extensions sidebar): 2018.9.0
• OS and version: Linux Mint 19 x64
• Python version (& distribution if applicable, e.g. Anaconda): 3.6.6
• Type of virtual environment used (N/A | venv | virtualenv | conda | …): N/A
• Relevant/affected Python packages and their versions: N/A

Actual behavior

When working in a workspace that has no associated folder, nearly all python.xxx commands fail with a “not found” error. The only exception seems to be python.setInterpreter, which works fine.

When the window is not part of a workspace or when adding a folder to the workspace, the extension instantly resumes full functionality.

Expected behavior

The extension used to work fine with workspaces that have no associated folders.

Steps to reproduce:

1. Install the extension, if necessary
2. File > New Window
3. File > Save Workspace As
4. View > Command Palette, try to run any Python command other than Select Interpreter and see it fail
5. File > Add Folder to Workspace
6. Try step 3 again and see it succeed

Logs

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

n/a

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)

Error: command 'python.setLinter' not found
    at t._tryExecuteCommand (/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:3030)
    at /usr/share/code/resources/app/out/vs/workbench/workbench.main.js:3029
    at n.Class.derive._oncancel.then (/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:167)
    at t.executeCommand (/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:3029)
    at t.run (/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:1366)
    at t.run (/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:1367)
    at /usr/share/code/resources/app/out/vs/workbench/workbench.main.js:3015

[gm10]

Didn’t realize this one was still open, I believe this was fixed a while ago actually.

[gm10]

Ah good. In that case I added a PR that fixes it on my end @DonJayamanne . Disclaimer: I know nothing about your code base, additional changes may be required elsewhere.