# Python lsp broken after update to Cursor 1.0 **URL:** \ **Category:** Bug Reports\ **Created:** [June 5, 2025, 8:11pm UTC](https://forum.cursor.com/t/python-lsp-broken-after-update-to-cursor-1-0/100824 "2025-06-05T20:11:12Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![jscheel](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jscheel/32/61399_2.png) [@jscheel](https://forum.cursor.com/u/jscheel)\ **Post date:** [June 5, 2025, 8:11pm UTC](https://forum.cursor.com/t/python-lsp-broken-after-update-to-cursor-1-0/100824/1 "2025-06-05T20:11:12Z")
Just updated to the new 1.0 release. Now I get the error: “Editor support is inactive since language server is set to None.” and my python lsp does not work. I’ve tried manually setting “python.languageServer”: “Pylance” in my settings, but it doesn’t help. Running MacOS 15.4.1. ---
**Author:** ![ravirahman](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/ravirahman/32/20386_2.png) [@ravirahman](https://forum.cursor.com/u/ravirahman)\ **Post date:** [June 6, 2025, 2:56pm UTC](https://forum.cursor.com/t/python-lsp-broken-after-update-to-cursor-1-0/100824/3 "2025-06-06T14:56:51Z")
Hi @jscheel, to use Pylance, that extension will need to be installed separately. Could you try searching for it in the marketplace? Attaching a screenshot. Thanks! ![image](https://us1.discourse-cdn.com/cursor1/original/3X/5/8/58dc75706bdce5e143109970bed5e27823104c17.png) ---
**Author:** ![ngage](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/ngage/32/61678_2.png) [@ngage](https://forum.cursor.com/u/ngage)\ **Post date:** [June 6, 2025, 4:03pm UTC](https://forum.cursor.com/t/python-lsp-broken-after-update-to-cursor-1-0/100824/4 "2025-06-06T16:03:50Z")
bumping this, the LSP is regularly timing out (not OOM) with both pylance & jedi. ---
**Author:** ![jscheel](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jscheel/32/61399_2.png) [@jscheel](https://forum.cursor.com/u/jscheel)\ **Post date:** [June 6, 2025, 6:30pm UTC](https://forum.cursor.com/t/python-lsp-broken-after-update-to-cursor-1-0/100824/6 "2025-06-06T18:30:45Z")
Yep, this is happening with pylance installed. It does not happen with based-pyright though. I should say that the log I quoted earlier may be a red-herring, as it happens when based-pyright is running too. So it may just be timing out, like @ngage said. ---
**Author:** ![ravirahman](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/ravirahman/32/20386_2.png) [@ravirahman](https://forum.cursor.com/u/ravirahman)\ **Post date:** [June 7, 2025, 7:02pm UTC](https://forum.cursor.com/t/python-lsp-broken-after-update-to-cursor-1-0/100824/8 "2025-06-07T19:02:08Z")
Hi! If it is timing out, I’d recommend configuring exclude (or specific include) directories – that will reduce the # of files the LSP has to analyze. If you’re using Cursor Pyright (which is based on basedpyright), the setting is `cursorpyright.analysis.exclude`; if you’re on Pylance, the setting is `python.analysis.exclude`. ---
**Author:** ![jscheel](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jscheel/32/61399_2.png) [@jscheel](https://forum.cursor.com/u/jscheel)\ **Post date:** [June 8, 2025, 5:27pm UTC](https://forum.cursor.com/t/python-lsp-broken-after-update-to-cursor-1-0/100824/9 "2025-06-08T17:27:35Z")
I’m not sure about timing out. For me specifically, it completely ceased to work where it was previously working in the exact same directory just before the upgrade to 1.0. ---
**Author:** ![ngage](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/ngage/32/61678_2.png) [@ngage](https://forum.cursor.com/u/ngage)\ **Post date:** [June 10, 2025, 2:51pm UTC](https://forum.cursor.com/t/python-lsp-broken-after-update-to-cursor-1-0/100824/11 "2025-06-10T14:51:06Z")
I already aggressively exclude files & folders; currently analysis is on ~800-900. With both cursorpyright & Pylance, Cursor 1.0 is completely unusable. I have inlay hints & semantic coloring enabled, fwiw. I’ve downgraded to 0.53 for the time being. I believe this may be an issue with pydantic / pydantic-ai, which have known issues with LSPs (for example, mypy analysis is disabled in pydantic), perhaps there’s something Cursor is doing which is causing very slow analysis? @jscheel can you confirm if you’re using pydantic-\* packages in said codebase? ---
**Author:** ![jscheel](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jscheel/32/61399_2.png) [@jscheel](https://forum.cursor.com/u/jscheel)\ **Post date:** [June 10, 2025, 5:27pm UTC](https://forum.cursor.com/t/python-lsp-broken-after-update-to-cursor-1-0/100824/13 "2025-06-10T17:27:25Z")
Yep, pydantic is definitely there. It works its way into everything 🙂 ---
**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\ **Post date:** [July 10, 2025, 5:28pm UTC](https://forum.cursor.com/t/python-lsp-broken-after-update-to-cursor-1-0/100824/15 "2025-07-10T17:28:33Z")
Closed on July 10, 2025, 5:28pm UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.