python-language-server

I do fault them, a bit, philosophically, but that’s not even the core of my complaint here. I may not like Microsoft releasing proprietary software, but I hardly feel surprised or cheated when they do. On the other hand, when Microsoft creates an interoperability standard to solve the proliferation of wheel-inventing in IDEs, actively promotes it as such, creates and supports an open-source implementation of it for Python as part of said promotion, then abandons[1] said implementation in favour of a proprietary one that deliberately speaks the interoperability protocol in a slightly non-interoperable way, then yes, I do feel like I’ve been conned, and maybe I should stop treating Microsoft’s open-source efforts seriously even if they’re good software at the present moment. (Whether my level of cynicism regarding Microsoft should have been

How about the fact that some extensions like Remote Development [1] and LiveShare [2] work only on proprietary builds of vscode, and not on code-oss or vscodium? I get it that those are proprietary extensions, but they still show up in the extension marketplace for OSS builds. And I don't see a technical reason why they wont run on OSS builds, other than that the extension builders want it that way. And these extensions are important enough that you will end up downloading the proprietary build while you are too busy solving something with your team mates. This is a very subtle way to push even privacy-aware developers to use the proprietary build with built-in telemetry. And how about the fact that the de-facto reference implementation of LSP client (most language servers are developed against vscode) uses many undocumented and non-stand

Well there is Pyright by MS (that's what Pylance is based on) and python-language-server by MS - that one has been superseded by Pyright and is deprecated in Code. https://github.com/microsoft/pyright https://github.com/Microsoft/python-language-server The only(?) one not by MS is Jedi: https://github.com/pappasam/jedi-language-server

This title is inaccurate. The language server _is_ open source, and is available here: https://github.com/microsoft/python-language-server. This is the default one VSCode ships with. This issue is filed on Pylance, a new (released June 2020) language server that's currently still in beta (announcement: https://devblogs.microsoft.com/python/announcing-pylance-fas...). Also, like the contributor notes, a lot of the "secret sauce" in Pylance is part of the open source Pyright typechecker: https://github.com/microsoft/pyright.

The same team that does a bulk of the "python" language service dev for VS Code did the main plugin for python development in Visual Studio. It was actually pretty good. https://github.com/Microsoft/python-language-server https://github.com/Microsoft/PTVS

I have used both softwares but stick with VSCode for Python, simply because it is very powerful to have one great editor for all projects, as opposed to one specialized IDE for each. PyCharm is (AFAIK) monolithic in what it brings to the table, whereas VSCode is more modular. As such, some of your points are true, but not an inherit fault of VSCode, but probably of some settings/underlying tools used. Maybe these can get you a better experience: 3. Agreed with VSCode being lackluster, but switching to MS Language Server [0] has helped this a great deal (while having other downsides, like being slower). 5. VSCode also has a variable viewer/browser and an interactive shell (which cannot be IPython as of today, however [1]) 6. Disagree: I forgot what VSCode uses per default, but I switched to `black` for formatting, which works very well (`

Please file issues as you find regressions at https://github.com/microsoft/python-language-server as the team is working diligently to fix such issues.

Interesting, as I was thinking about going back to Sublime after being frustrated by the Python Language Server eating RAM like a Gremlin after midnight. https://github.com/Microsoft/vscode-python/issues/2594 https://github.com/Microsoft/python-language-server/issues/4... https://github.com/Microsoft/vscode/issues/65639 https://github.com/Microsoft/vscode-python/issues/2553

The same engine that VSCode uses is open source [1]. With lsp-mode [2] or eglot [3], you can have the same stuff working inside emacs. I've actually been writing Java inside emacs lately --- yes, java, and I have had very few issues. One caveat, development on the emacs LSP stuff is moving very quickly, so I don't recommend using ELPA/MELPA/etc. to install the plugins. I use straight.el [4] to manage my plugins, they're checked out from the upstream source and can be updated at-will. You'll also need an up to date version of emacs, ie: 26+. (That's the current release, but it's not available in some distributions ie: debian/ubuntu yet.) --- [1]: https://github.com/Microsoft/python-language-server [2]: https://github.com/emacs-lsp/lsp-mode [3]: https://github.com/joaotavora/eglot [4]: https://github.com/raxod502/straight.el