Python extension not starting Pylance

[andrew-dragoslavic]

I am trying to use python on the newest VS Code version on my macbook and no matter what I do the Pylance Intellisense isnt working. When I hover over methods it doesn't show anything and there is no suggestions for methods to use. I have looked through my settings.json to try to find what the issue is and have even tried reinstalling VS Code from scratch with the proper extensions multiple times and nothing is working.

[github-actions]

Hi @andrew-dragoslavic, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

---

Potential Duplicate Issues – These issues may be duplicates of your report, but may differ in some of the details.

• Python intellisense not working – macOS, virtual environment selected but no IntelliSense returns. Python intellisense not working pylance-release#5851
• IntelliSense/Pylance Semantic Highlighting and auto-code-completion is not working – M-series macOS, reinstalled VS Code, no highlighting or suggestions. IntelliSense/Pylance Semantic Highlighting and auto-code-completion is not working pylance-release#5850
• Tooltip suggestions don't show up – disabling Pylance restores tooltip suggestions. Tooltip suggestions don't show up. pylance-release#4213
• Intellisense not working when using pylance (no suggestions Ctrl+Space) – Windows 10, venv, no suggestions for simplekml. Intellisense not working when using pylance (no suggestions Ctrl+Space) pylance-release#5689

---

The team will respond to your issue shortly. Please note this is a trial feature and may not be fully accurate. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or was incorrect, please give it a 👎. Your feedback helps us improve!

[rchiodo]

The log in the 'output' tab should give some indication of what the problem is. It should be here:

In the past this is usually one of:

• Your "python.languageServer" setting is not "Default", or "Pylance". We've seen lately that running cursor will actually force it to "None"
• You're running an open source version of VS Code (or fork) where our license doesn't allow us to run
• The Python extension somehow fails to start, making Pylance not start

[andrew-dragoslavic]

I am not able to see python language server is Python the same thing?

If so this is the Python output

[rchiodo]

I would hazard a guess your "python.languageServer" setting is None. Potentially because Cursor wrote it that way. We've noticed that lately they write "python.languageServer" to a ".vscode/settings.json" file.

[rchiodo]

Otherwise there should be an entry in the "Python" output tab saying it's starting the language server, and the "Python Language Server" tab should be there.

[andrew-dragoslavic]

I did not originally have a settings.json but i added one to the folder and set the language server to Pylance but I am still not seeing anything about a language server starting.

[rchiodo]

What does this show:

[andrew-dragoslavic]

It is set to Pylance

[rchiodo]

What does the extensions tab show for Pylance?

If it's enabled, it seems like the Python extension isn't starting it for some reason.

[andrew-dragoslavic]

This is what mine shows

[rchiodo]

This is likely a Python extension error then. They're not starting us. Transferring there.

[rchiodo]

@andrew-dragoslavic can you look in the 'Help | Developer Tools' console and see if you see something like so:

ERR Extension 'ms-python.vscode-pylance' wants API proposal 'mcpConfigurationProvider' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.

Oh nevermind, that comes up for me too, but it doesn't prevent us from loading.