omicverse-notebook
JupyterLab plugin that brings the omicverse-web DataFrame and AnnData preview ideas into a standalone package.
It provides:
- Rich output renderers for
pandas.DataFrame,pandas.Series, andanndata.AnnData - A JupyterLab command that opens an
OmicVerse Notebookpanel for inspecting kernel variables by name - Automatic formatter activation for the active notebook or console kernel when the JupyterLab frontend extension is loaded
- Color-coded DataFrame columns, sticky headers, compact shape cards, and AnnData slot summaries
Scope
This package intentionally focuses on the display layer:
- kernel-side Python helpers turn variables into JSON preview payloads
- JupyterLab frontend plugins render those payloads and provide a lightweight inspector UI
It does not depend on the omicverse-web Flask APIs.
Install
Development install:
cd omicverse-notebook
pip install -e .
For an end-user install, build a wheel first so the prebuilt labextension is bundled:
cd omicverse-notebook
jlpm install
jlpm build:prod
pip install .
Enable rich output
If the frontend extension is loaded correctly, it will try to enable formatters automatically for the active notebook or console kernel.
Manual fallback:
%load_ext omicverse_notebook
Or:
from omicverse_notebook import enable_formatters
enable_formatters()
After that, displaying a DataFrame or AnnData object in a notebook cell will use the OmicVerse renderers.
Inspector usage
Open Command Palette and run:
OmicVerse Notebook: Open
If rich output still does not appear in an already-running kernel, run:
OmicVerse Notebook: Enable Kernel Formatters
Then inspect variables like:
df
adata
adata.obs
adata.layers["counts"]
adata.obsm["X_umap"]
Notes
- The inspector executes a small helper snippet in the current kernel and expects the Python package to be installed in that kernel environment.
- AnnData is optional on install, but AnnData previews only activate if
anndatais available in the kernel.
Metadata
Release files for omicverse-notebook 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| omicverse_notebook-0.1.4.tar.gz | 783.4 kB | Without provenance | Details for omicverse_notebook-0.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| omicverse_notebook-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for omicverse_notebook-0.1.4-py3-none-any.whl |
Total release size: 1.6 MB
Release files / omicverse_notebook-0.1.4.tar.gz
| Download URL | omicverse_notebook-0.1.4.tar.gz |
|---|---|
| Size | 783.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f1acf970a2cd4efe7318604a51fcc8b7f4402613d969c6b9c1d471ad31c3871a
|
|
BLAKE2b-256 checksum How to use checksums |
e0a85b2b723e1f3ae72bcae24d5b80cabed306d37716ef8348293807c2d3b117
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.10
|
Release files / omicverse_notebook-0.1.4-py3-none-any.whl
| Download URL | omicverse_notebook-0.1.4-py3-none-any.whl |
|---|---|
| Size | 794.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1f4b8e3df0e9e2f465da7b605d0ecedcb9b9f8b0191bd730b0c25e7f1ac6f3f9
|
|
BLAKE2b-256 checksum How to use checksums |
10e3ce76a0f307bb94e218781e0fbf41167161dd151ca04dfed916f9addb8e08
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.10
|
Security for omicverse-notebook 0.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.