Open Source Python Language Servers

clangd understands your C++ code and adds smart features to your editor: code completion, compile errors, definition, and more. clangd is a language server that can work with many editors via a plugin. Here’s Visual Studio Code with the clangd plugin, demonstrating code completion.

Woke is a Python-based development and testing framework for Solidity. A testing framework for Solidity smart contracts with Python-native equivalents of Solidity types and blazing-fast execution. A property-based fuzzer for Solidity smart contracts that allows testers to write their fuzz tests in Python. See examples and documentation for more information. Fuzzer builds on top of the testing framework and allows efficient fuzz testing of Solidity smart contracts. Woke implements an LSP server for Solidity. The only currently supported communication channel is TCP.

HDL Checker is a language server that wraps VHDL/Verilg/SystemVerilog tools that aims to reduce the boilerplate code needed to set things up. It supports Language Server Protocol or a custom HTTP interface; can infer the library VHDL files likely to belong to, besides working out mixed language dependencies, compilation order, interpreting some compiler messages and providing some (limited) static checks. Notice that currently, the unused reports has caveats, namely declarations with the same name inherited from a component, function, procedure, etc.

Fork of the python-language-server project, maintained by the Spyder IDE team and the community. A Python 3.7+ implementation of the Language Server Protocol. The base language server requires Jedi to provide Completions, Definitions, Hover, References, Signature Help, and Symbols. Like all language servers, the configuration can be passed from the client that talks to this server (i.e. your editor/IDE or another tool that has the same purpose). The details of how this is done depend on the editor or plugin that you are using to communicate with python-lsp-server. The configuration options are available at that level are documented in CONFIGURATION.md. Overall configuration is computed first from user configuration (in home directory), overridden by configuration passed in by the language client, and then overridden by configuration discovered in the workspace.