Skip to content

LSP support to 3rd-parties #21964

Closed
Closed

Description

No description provided.

Activity

  1. modified the milestones: November 2023, on Nov 27, 2023
  2. removed this from the milestone on Dec 11, 2023
  3. trinhanhngoc commented on Jan 25, 2024

    @trinhanhngoc

    Hello Karthik Nadig (@karthiknadig) ,

    I am a bit curious about this issue. Does it mean that the Python extension will allow using other contributed language servers besides Jedi and Pylance?

  4. karthiknadig commented on Jan 25, 2024

    @karthiknadig
    MemberAuthor

    Trịnh Anh Ngọc (@trinhanhngoc) This was to provide support tools using the following products:

    1. This code generator for LSP types in various languages: https://github.com/microsoft/lsprotocol . This was to standardize and make it easier for Server implementers to ingest changes to LSP specification.
    2. LSP types packages for various languages. These are concrete packages that we publish that LSP implementers can depend on
    3. Template for VS extension for python based tools: https://github.com/microsoft/vscode-python-tools-extension-template . This template allows you to create an extension for VS Code, with tools running in python.

    With the above three things, you could contribute a Language Server of your own. You can turn off the ones that are shipped with python extension ("python.languageServer" : "None"), and run one of your own. Note that this was never something that was blocked. The only thing the above 3 things did was to make it lot easier to create LSP based VS code extensions (see Ruff Extension a 3rd party Linting and formatting extension based on Ruff). The Jedi language server that we use is also based on the above packages (jedi-language-server)

    If you want to create your own server and would like to use our template here is a video (live stream) where I show how to do it:

    All of this was meant to be is a quick starting point to and move the interesting part of LSP development into Python or Rust.

  5. trinhanhngoc commented on Jan 26, 2024

    @trinhanhngoc

    Karthik Nadig (@karthiknadig) , Many thanks for the detailed explanation.

  6. locked as resolved and limited conversation to collaborators on Feb 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

feature-requestRequest for new features or functionalityneeds PRReady to be worked on

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions