vscodium: python extension - interpreter selector not showing on status bar

Describe the bug Interpreter selector don’t show when open a python file.

Please confirm that this problem is VSCodium-specific

  • This bug doesn’t happen if I use Microsoft’s Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn’t already documented

To Reproduce Steps to reproduce the behavior:

  1. Open a Python file and wait for the extension to activate. Notice the interpreter not showing on the status bar.

Screenshots

Expected behavior InterpreterSelectionZoom

Actual behaviour Screenshot_20201013_231159

The extension is activated (it even activates my virtual environment when I create a new terminal) and working normally, I just can’t see the interpreter on the status bar.

Desktop (please complete the following information):

  • OS: [ Arch Linux ]
  • Architecture [ x64 ]
  • Version [ 1.50.0 ]

Additional context

Logs: Output for Python in the Output panel:

User belongs to experiment group 'ShowPlayIcon - start'
User belongs to experiment group 'ShowExtensionSurveyPrompt - control'
User belongs to experiment group 'DebugAdapterFactory - experiment'
User belongs to experiment group 'PtvsdWheels37 - experiment'
User belongs to experiment group 'UseTerminalToGetActivatedEnvVars - control'
User belongs to experiment group 'LocalZMQKernel - experiment'
User belongs to experiment group 'CollectLSRequestTiming - control'
User belongs to experiment group 'CollectNodeLSRequestTiming - experiment'
User belongs to experiment group 'EnableIPyWidgets - experiment'
User belongs to experiment group 'RunByLine - control'
User belongs to experiment group 'CustomEditorSupport - control'
User belongs to experiment group 'pythonaacf'
> conda --version
> pyenv root
> python3.7 ~/.vscode-oss/extensions/ms-python.python-2020.9.112786/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python3.6 ~/.vscode-oss/extensions/ms-python.python-2020.9.112786/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python3 ~/.vscode-oss/extensions/ms-python.python-2020.9.112786/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python2 ~/.vscode-oss/extensions/ms-python.python-2020.9.112786/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python ~/.vscode-oss/extensions/ms-python.python-2020.9.112786/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> ~/venv/python3.8/bin/python ~/.vscode-oss/extensions/ms-python.python-2020.9.112786/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> conda info --json
Error 2020-10-13 23:38:25: Failed to check if file needs to be fixed [EntryNotFound (FileSystemError): '/home/julius/.config/Code/User/settings.json' (EntryNotFound (FileSystemError): Error: ENOENT: no such file or directory, open '/home/julius/.config/Code/User/settings.json')
	at _handleError (/usr/share/vscodium-bin/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:725:473)
	at processTicksAndRejections (internal/process/task_queues.js:94:5)
	at async y.readText (/home/julius/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:1:498547)
	at async p.doesFileNeedToBeFixed (/home/julius/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:56:961593)
	at async /home/julius/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:56:960720
	at async Promise.all (index 0)
	at async p.getFilesToBeFixed (/home/julius/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:56:960666)
	at async p.updateTestSettings (/home/julius/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:56:960293)] {
  code: 'FileNotFound',
  name: 'EntryNotFound (FileSystemError)'
}
> ~/venv/python3.8/bin/python ~/.vscode-oss/extensions/ms-python.python-2020.9.112786/pythonFiles/pyvsc-run-isolated.py -c "import notebook"
> ~/venv/python3.8/bin/python ~/.vscode-oss/extensions/ms-python.python-2020.9.112786/pythonFiles/pyvsc-run-isolated.py -c "import jupyter"
Starting Jedi Python language engine.
Python interpreter path: /home/julius/venv/python3.8/bin/python
Error 2020-10-13 23:38:26: Python Extension: interpreterManager.refresh [Error: [ms-python.python]: Proposed API is only available when running out of dev or with the following command line switch: --enable-proposed-api ms-python.python
	at a (/usr/share/vscodium-bin/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:655:99)
	at Object.t.checkProposedApiEnabled (/usr/share/vscodium-bin/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:655:567)
	at Object.get activeNotebookEditor [as activeNotebookEditor] (/usr/share/vscodium-bin/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:1003:116)
	at u.get activeNotebookEditor [as activeNotebookEditor] (/home/julius/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:54:383170)
	at u.get hidden [as hidden] (/home/julius/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:56:642106)
	at /home/julius/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:56:844423
	at Array.every (<anonymous>)
	at g.updateVisibility (/home/julius/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:56:844411)
	at g.updateDisplay (/home/julius/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:56:844284)
	at async g.refresh (/home/julius/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:56:843237)]

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 9
  • Comments: 20 (4 by maintainers)

Most upvoted comments

I just bumped into this issue on my vscodium v1.64.0 and ms-python v2022.0.1786462952 (on my 5.10.96-1-MANJARO). I tried to re-install ms-python extension, but it didn’t resolve the issue. What logs could I share to help you see what’s going on here?

Version: 1.64.0
Commit: 5554b12acf27056905806867f251c859323ff7e9
Date: 2022-02-04T06:27:19.879Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Linux x64 5.10.96-1-MANJARO

Was this fixed for everyone when using a 2021 version of the extension?

Yep, I’m getting the issue when using the version 2020.10.332292344 (the latest on open-vsx). But when using the latest version from the VS Code Marketplace, I don’t have the issue

Here how to switch of marketplace

Hi there, the issue is fixed for me now on

Version: 1.52.0
Commit: 940b5f4bb5fa47866a54529ed759d95d09ee80be
Date: 2020-12-12T00:37:51.866Z
Electron: 9.3.5
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Linux x64 5.9.13-200.fc33.x86_64

Screenshot from 2020-12-12 09-07-13

Yeah I confirm that the 2021 version from the official marketplace solves the issue. That indicates that a few weeks ago a regression snuck in, because the 2020 version was able to display the Python interpreter, the problem came back a few weeks ago (to clarify, the 2020 version was not able to show the interpreter, then it worked again, and stopped working again a few weeks ago)

Thanks for the hint, I can confirm that this fixes the issue.