Upstream software project

python-jupyter-lsp

LSP for Jupyter Notebook/Lab server

About python-jupyter-lsp

LSP for Jupyter Notebook/Lab server

This project links 3 native package records across 1 recorded operating-system release. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

openSUSE Tumbleweed: 3 package records. Catalog coverage diagram, not an application screenshot.python-jupyter-lsp: recorded package coverageopenSUSE Tumbleweed3 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
python-jupyter-lsp
Publisher
Not authoritatively mapped
Native package records
3
Operating systems
opensuse-tumbleweed
License expression
BSD-3-Clause
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

Multi-Language Server WebSocket proxy for Jupyter Notebook/Lab server Jupyter config

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

openSUSE Tumbleweed

  1. Package jupyter-lsp

    tumbleweed (openSUSE Tumbleweed) (Unspecified): LSP for Jupyter Notebook/Lab server - Config

    5.2.0-3.4: noarch

    Source: python-jupyter-lsp

  2. Package python313-jupyter-lsp

    tumbleweed (openSUSE Tumbleweed) (Unspecified): LSP for Jupyter Notebook/Lab server

    2.2.6-3.4: noarch

    Source: python-jupyter-lsp

  3. Package python314-jupyter-lsp

    tumbleweed (openSUSE Tumbleweed) (Unspecified): LSP for Jupyter Notebook/Lab server

    2.2.6-3.4: noarch

    Source: python-jupyter-lsp

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.