Announcing Pylance: Fast, feature-rich language support for Python in Visual Studio Code #2096

Activity

1. Hugues Valois (huguesv)

   pinned this issue on Jun 30, 2020
3. huguesv commented on Jul 1, 2020

   

   Hugues Valois (huguesv)

   on Jul 1, 2020

   ContributorAuthor

   More actions

   @jaguarest please see microsoft/pylance-release#16

   👍React with 👍1Reacted by Russell Johnson
4. d0mf1g commented on Jul 3, 2020

   

   d0mf1g

   on Jul 3, 2020

   More actions

   So I take it that this repo will eventually be deprecated as work moves to improving Pylance?

   👍React with 👍1Reacted by AJ
5. CatNofishing commented on Jul 4, 2020

   

   Cat (CatNofishing)

   on Jul 4, 2020

   More actions

   Awesome! Great Job! 😁
6. Seirdy commented on Jul 25, 2020

   

   Seirdy

   on Jul 25, 2020

   More actions

   Hugues Valois (@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).

   👍React with 👍10Reacted by Shane Kennedy, Sergei Ivashchenko, Feraidoon Mehri, Kurt Wilson, kuator, Chetan Koneru, Alessandro Re, Rajan Ponnappan, James Nelson and AJ
7. savannahostrowski commented on Jul 30, 2020

   

   Savannah Ostrowski (savannahostrowski)

   on Jul 30, 2020

   Last edited by savannahostrowski

   More actions

   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.

   😕React with 😕1Reacted by Takuma Yoneda
8. noelevans commented on Jul 30, 2020

   

   Noel Evans (noelevans)

   on Jul 30, 2020

   More actions

   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.
9. Seirdy commented on Jul 30, 2020

   

   Seirdy

   on Jul 30, 2020

   Last edited by Seirdy

   More actions

   Depending on your use case, you might also be interested in checking out Pyright
   (which powers the Pylance language server) or forking this repo.

   Thanks for the heads-up, Savannah Ostrowski (@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.
10. Kurtoid commented on Aug 10, 2020

    

    Kurt Wilson (Kurtoid)

    on Aug 10, 2020

    Last edited by Kurtoid

    More actions

    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

    👍React with 👍43Reacted by Nils K, Chetan Koneru, Dale Sedivec, cbrown, Ellison, Andrew Christianson, Matt Webster, Mischa Spiegelmock, Ross A. Baker, Hunter and 33 more
11. DoS007 commented on Apr 11, 2021

    

    DoS007

    on Apr 11, 2021

    Last edited by DoS007

    More actions

    Hmm, that sounds a bit like microsoft's old strategy: https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish .

    I think Microsoft's whole purpose with creating vscode and especially the "language server protocol"(LSP) is to apply their "embrace, extend, extinguish" strategy on code editors. They created a cool code editor with a cool concept called LSP. The editor quickly becomes the most popular editor in the world since its "open source". Most other editors shift to using LSP coz it becomes a standard for editor-agnostic code diagnostics. This is the "embrace" part.

    Microsoft slowly breaking their own protocol (I have seen a few blog posts of LSP-client developers complaining about vscode breaking its own protocol and that language-servers tend to follow vscode and not the LSP standard). This is the extend part.

    Microsoft, if successful, might try to extinguish all open source editors by breaking LSP more and more, making the development process of competing editors harder and harder since they completely rely on LSP for diagnostics. on the meantime, they might make vscode more and more closed source (and start by making its extensions more and more closed). This is the extinguish part.

    Source

    Hopefully this won't happen.

    👍React with 👍10Reacted by Salomon Popp, Emil J, Jakub Vaněk, Ben Mares, James Nelson, Manoj Baishya, smekkley, Eugene Platonov, bugsbugsbux and David Chkhikvadze

    👀React with 👀3Reacted by Ben Mares, James Nelson and Tomer Chachamu