python-language-server VS pylance-release

I use neovim as a text editor and code a lot in Python with the help of a language server. I use the only language server that seems to live in python-language-server. However, I see that the repo that it points to has been archived. So I am looking for alternatives and I thought that asking the community could be a good starting point.

Ah, in any case you might like to know they do plan to deprecate it in favour of pyright/pylance.

I guess this is an issue not only on my side - https://github.com/microsoft/python-language-server/issues/2108

I followed the advice given by this, but it didn't help..

I was a longtime user of Sublime Text and switched to VSCode because of Remote Development and Pylance. Everything else is pretty much fine and Sublime has always had better performance, though these days having support for AI integration (a la Copilot) is also necessary for me.

I tried Zed recently because it has remote support and AI integration, but the Python integration is limited to Pyright so I gave up temporarily (I guess I can recreate Pylance using this doc: https://github.com/microsoft/pylance-release/blob/main/USING...).

a very important difference is that MS doesn't let you use some of their quite nice language servers unless you're using VS Code, e.g. Pylance: https://github.com/microsoft/pylance-release/issues/483

for this reason, the non-MS-built VS Code isn't equivalent to theirs, regardless of the license of the editor itself.

One of the things that comes to mind here is the fact that the default Python extension for VS Code is, perhaps surprisingly to many, not open source. https://github.com/microsoft/pylance-release

While it's possible to fork VS Code, it is not possible to fork VS Code and provide a seamless onramp towards a Python editing experience that is fully open source, because users are used to the nuances of the closed-source Pylance experience in VS Code proper. You could use the minified/compiled Pylance plugin in your fork, but you'd have no way to expand its capabilities to new hooks your fork provides. Microsoft's development process would always be able to move faster than a fork, because it could coordinate VS Code internal API development with its internal Pylance team, and could become incompatible with forks at any time.

It's worth re-reading the quote from J Allard in https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis... with this modern example in mind.

(Also worth mentioning https://github.com/detachhead/basedpyright?tab=readme-ov-fil... which is a heroic effort to derisk this, but it's an uphill battle for sure!)

Anyone know how can we fix this issue if we build the vscode locally

Do any of these issue tickets explain the behaviour you're seeing? https://github.com/microsoft/pylance-release/issues/4341, https://github.com/microsoft/pylance-release/issues/4071

Maybe they "are the same thing" in terms of behavior (I don't know), but "A uses B" doesn't mean that "A is B".

One important difference in this case is that while "Pylance leverages Microsoft's open-source static type checking tool, Pyright" [1], Pylance itself is not open source. In fact, the license [2] restricts you to "use [...] the software only with [...] Microsoft products and services", which means that you are not allowed to use it with a non-Microsoft open source fork of VS Code, for example.

The license terms also say that by accepting the license, you agree that "The software may collect information about you and your use of the software, and send that to Microsoft" and that "You may opt-out of many of these scenarios, but not all".

[1] https://github.com/microsoft/pylance-release

[2] https://marketplace.visualstudio.com/items/ms-python.vscode-...