René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Update: Version 2.0 → Migrate to pygls + Microsoft's lsprotocol + Save Document","articleBody":"# Overview\n\nTo align with Spyder IDE's remote development features (part of CZI 2022-316698 grant), the version 2.0 of the python's LSP server needs to support the latest LSP protocol version and allow to save document edditions on remote machines (enableling remote editing for Spyder). With this requirements, instead of relying on the current custom protocol implementation, it will be adopted Microsoft’s official **`lsprotocol`** package for Python. Also, the server will be refactored to use **`pygls`** for handling base TCP communications, features management and document management. This changes lays the foundation for a server more scalable, maintainable and robust, especially for remote environments.\n\n# Key Features\n\n* **Asyncio-based foundation with pygls**\n  The server leverages **pygls** as its base implementation, providing a robust asyncio-driven framework for building language servers in Python. This includes built-in support for feature and command registration, multiple connection modes (TCP, STDIO, WebSocket), and automatic handling of document lifecycle events (open, change, close).\n\n* **Standards-compliant typing with lsprotocol**\n  By adopting **lsprotocol**, the server uses officially maintained, up-to-date Python types that align directly with the evolving LSP specification. This ensures cleaner versioning, greater consistency, and reduced maintenance overhead compared to proprietary type definitions.\n\n* **Atomic document commit mechanism**\n  To enhance reliability in remote development workflows (such as Spyder), the server supports an **opt-in atomic commit feature**. Instead of persisting edits immediately, the server can hold them in memory until a custom command (e.g., `spyder/commitEdits`) is issued. This enables atomic persistence of edits, improving resilience against latency and partial failures.\n\n# **Roadmap**\n\n1. **Migrate to pygls**\n\n   * Replace the custom LSP scaffolding with **pygls** to serve as the event loop and request/notification dispatcher.\n   * Ensure existing LSP features (completion, hover, diagnostics, etc.) are re-registered using pygls’s feature/command decorators with current plugin architecture.\n   * Configure entry-points for TCP, STDIO, and WebSocket connection modes for compatibility with current server API.\n\n2. **Refactor configuration and plugin architecture**\n\n   * Adopt **lsprotocol** types across the plugins codebase for functions signatures ensuring alignment with the official LSP specification.\n   * Type check all plugins to ensure proper specification.\n   * Redesign configuration loading and plugin interfaces to extend the **pygls base server**, allowing external modules to register features more cleanly.\n\n3. **Implement atomic document commit support**\n\n   * Maintain in-memory buffers of document changes rather than writing them immediately to disk.\n   * Introduce a custom command (e.g., `server/commitEdits`) to atomically persist pending edits when requested.\n","author":{"url":"https://github.com/hlouzada","@type":"Person","name":"hlouzada"},"datePublished":"2025-09-12T20:38:37.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/671/python-lsp-server/issues/671"}