This happens at random moments: [Screenshot 2024-08-25 at 15.53.37] Version: 0.39.6 VSCode Version: 1.91.1 Commit: a4f99b7dfb14460cb0bcebd9f6ac7ca158217920 Date: 2024-08-19T00:03:08.275Z Electron: 29.4.0 ElectronBuildId: undefined Chromium: 122.0.6261.156 Node.js: 20.9.0 V8: 12.2.281.27-e…

An excessive solution that may work is ‘resetting cursor state’. The downside is it would clear your local chat history. Steps are: Quit Cursor rm -r ~/.cursor/extensions/* rm -rf ~/Library/Application\ Support/Cursor/ Open up Cursor and go through onboarding again/install relevant extensions I …

Fresh install, did all the steps you provided. Still stuck with a “Discovering Python Interpreters” Version: 0.40.4 VSCode Version: 1.91.1 Commit: 63dae81aea2c3fc079420fe72578a8eef26ba870 Date: 2024-09-05T02:52:05.660Z (5 days ago) Electron: 29.4.0 ElectronBuildId: undefined Chromium: 122.0.…

Also struggling with this and finding myself go back to VSCode so that i can jump to definition and get the amazing syntax highlighting i’m used to from Pylance. I use direnv for managing python environments and that all works perfectly fine in VSCode. ersion: 0.40.4 VSCode Version: 1.91.1 Commi…

I was having problems with the interpreters doing being discovered. All I had to do was to switch the jupyter (ms-toolsai) to pre-release and then it was able to find my interpreters.

So I was having this issue on one user on my machine and not another. Turned out that cursor was installing the universal versions of the python extensions in the broken profile and the darwin-arm64 versions in the one that works fine. Still trying to identify how you can force darwin-arm64 version…

Same Problem here. In VS Code it is working, but not in Cursor. Version: 0.41.3 VSCode Version: 1.91.1 Commit: 51c8aff7cb5a89f4a0e462fbacab938bdbfaf140 Date: 2024-09-25T17:13:50.377Z Electron: 29.4.0 ElectronBuildId: undefined Chromium: 122.0.6261.156 Node.js: 20.9.0 V8: 12.2.281.27-electro…

I just took another stab at resolving this and it seems to have worked: [image] I saw a lot of old python versions in my ~/.pyenv, so i went and deleted everything older than 3.11 and now it’s all working nicely and no longer stuck on “Discovering Python interpreters” I never directly use these …

That worked for me too! :heart_eyes: :heart_eyes:

I also got hit by this and had to take a couple of additional steps to get this sorted. This is on an M1 Mac. Started with fresh install, with extensions set up from scratch. Then “Discovering Python Interpreters” got stuck as soon as I installed the Python extension. I had a few different Python …

Discovering Python Interpreters stucks forever

Support Bug Reports

philipjames44 (Phil) September 26, 2024, 8:18pm 10

Im still having this issue on an M1 chip after going through all of the above. Im surprised there aren’t more people experiencing this.

Topic		Replies	Views
Select python interpreter does see my interpreters Bug Reports python , language-servers	4	701	January 29, 2026
"Discovering Python Interpreters" spins indefinitely and never resolves Bug Reports extensions , macos , python	2	207	February 11, 2026
I cannot select my venv python interpreter Bug Reports	9	3318	December 6, 2025
Python extension failed Bug Reports	4	213	April 28, 2025
Python: Select Interpreter not applying to terminal Bug Reports	0	1797	January 5, 2025

Discovering Python Interpreters stucks forever

Related topics