-
Notifications
You must be signed in to change notification settings - Fork 133
Announcing Pylance: Fast, feature-rich language support for Python in Visual Studio Code #2096
Comments
after installing pylance, and setting it as default language server, I get this problem in my setting.json, my code version is: |
@jaguarest please see microsoft/pylance-release#16 |
So I take it that this repo will eventually be deprecated as work moves to improving Pylance? |
Awesome! Great Job! 😁 |
@huguesv will the MPLS (this repository) continue to be maintained in the future? I ask because I use language servers with Neovim's built-in LSP client implementation, not VSCode. It looks like Pylance won't be open-sourced, which will make building/packaging/running it difficult on many platforms. If that is the case, many users of MPLS who use LSP clients besides VSCode will have to migrate over to palantir/python-language-server (slow), muffinmad/anakin-language-server, or pappasam/jedi-language-server (limited functionality, but can be combined with diagnostic-langserver for diagnostics and formatting). |
Hey @Seirdy Our team's plan is to transition users in VS Code over to Pylance. After that, this repository will no longer be maintained, at which point you would have to migrate over to another open-source option. Depending on your use case, you might also be interested in checking out Pyright (which powers the Pylance language server) or forking this repo. |
What an amazing decision. The idea of LSPs was created by Microsoft. I've watched YouTube videos of Microsoft employees lauding their achievements in this space. MPLS was the clear winner for Python against the existing options. What a lame outcome. |
Thanks for the heads-up, @savannahostrowski Having some documentation on using Pyright as an editor-agnostic language server and/or seeing more support in other LSP clients (cf neovim/nvim-lsp#303) to aid in migration before this repository is archived would be appreciated. |
I'm not a fan of migrating from an Open Source solution to a closed-source one. It's nice that Pyright is OSS, but I'm skeptical of Pylance |
Hmm, that sounds a bit like microsoft's old strategy: https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish .
Hopefully this won't happen. |
We are excited to announce Pylance, our fast and feature-rich language support for Python! Pylance is available today in the Visual Studio Code marketplace.
Please see the announcement for more details: https://devblogs.microsoft.com/python/announcing-pylance-fast-feature-rich-language-support-for-python-in-visual-studio-code/
If you are currently using VS Code with the Microsoft language server, we encourage you to give Pylance a try!
Please note that Pylance bugs should be filed at https://github.com/microsoft/pylance-release/issues
Thanks!
The text was updated successfully, but these errors were encountered: