Upstream software project

jupyter-kernel-test

A tool for testing Jupyter kernels

About jupyter-kernel-test

A tool for testing Jupyter kernels

This project links 4 native package records across 3 recorded operating-system releases. 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

jupyter-kernel-test repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Debian 12 (Bookworm): 1 package records; Debian 13 (Trixie): 1 package records; openSUSE Tumbleweed: 2 package records. Catalog coverage diagram, not an application screenshot.jupyter-kernel-test: recorded package coverageDebian 12 (Bookworm)1 recordsDebian 13 (Trixie)1 recordsopenSUSE Tumbleweed2 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
jupyter-kernel-test
Publisher
Not authoritatively mapped
Native package records
4
Operating systems
debian-12, debian-13, 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.

jupyter_kernel_test is a tool for testing Jupyter kernels. It tests kernels for successful code execution and conformance with the Jupyter Messaging Protocol.

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.

Debian 12 (Bookworm)

  1. Source: jupyter-kernel-test

Debian 13 (Trixie)

  1. Source: jupyter-kernel-test

openSUSE Tumbleweed

  1. Source: python-jupyter-kernel-test

  2. Source: python-jupyter-kernel-test

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.