It’s really disappointing that Cursor has even restricted search access to this article title on their forum.
This solve my issue as well! I just deleted all versions in ~/.pyenv because I wasn’t using any of them. Thanks!
Somewhat infuriatingly, this issue recently came back for me, for no apparent reason. I don’t have any random Python versions installed in Pyenv - just the one. No dead virtual environments or broken symlinks, like I had last time. Now just an infinite
Discovering Python Interpreters
whenever I fire up Cursor, which is unfortunately rendering it nearly useless 
Same thing, I’m on M3.
- Removing all extensions and going through setup again is a non-option for me.
- Nothing in ~/.local/share/virtualenvs (I’m using pyenv).
- Removed old versions of Python installed through pyenv, except a 2.X and the current one (3.13.5).
This started happening once I removed an existing .venv being used by cursor and re-created it inside a folder ‘utils’ in the current project (moving from root of a TS repo to an inner utils just for python). I’m using uv as package manager and tool to create the venv (after setting the local python version with pyenv local 3.13.5).
For now, I’ll have to use another IDE for Python, which is quite undesirable.
I hope we see a fix for this, as I really like the product.