pyviewarr
🤖 Clanker code disclaimer: written (largely) with large language model coding tools. Use at your own risk. 🤖
A faster, more intuitive way to explore 2D data (i.e. monochromatic images) in Python notebooks
Installation
pip install pyviewarr
or with uv:
uv add pyviewarr
Usage
First, open a notebook interface like JupyterLab (or another supporting anywidget).
Basic
pyviewarr.show() returns a widget instance. If it's the last line of your cell, it will display automatically.
import numpy as np
x = np.arange(16).reshape(4, 4)
pyviewarr.show(x)
Width and height of the widget can be set in the call to show():
pyviewarr.show(x, width=500, height=400)
You can also explicitly display with IPython.display.display():
widget = pyviewarr.show(x)
from IPython.display import display
display(widget)
If there are more than two axes, the last two axes are treated as Y and X (NumPy convention) and navigation buttons are shown for any others.
Navigating in a large datacube remains responsive because only one slice/image is sent to the viewer at a time.
Image stretching
Mapping array values to images for display involves normalization (stretching) which can include nonlinear transformations.
For all of these manipulations, you can reset them with the reset button:
Stretching
Right-clicking and dragging on the image viewer widget changes the contrast and bias. (If you have used ds9, this will feel familiar.)
Limits
When the image loads, the viewer sets the color limits to min(image) and max(image). Type in new limits if you want.
If you want to avoid resetting the limits (e.g. when paging through a data cube) use the lock button to fix the limits at their current values.
Linear/Log
Only three colormaps are included: gray, inferno, and magma (from matplotlib). Log stretch behaves like ds9 as well, such that negative values are rescaled and don't make invalid pixel values.
Diverging (±)
When examining residuals, you may want a diverging colormap centered at zero. Use the ± button to switch the limits to symmetric and the available colormaps to RdBu and RdYlBu (from matplotlib).
Zooming, panning, rotation
Zoom by clicking the +/- buttons at lower right, scrolling with your mouse/trackpad, or using the - and = keys. Reset zoom with the "reset zoom to fit" button or the 0 key.
Pan by clicking and dragging. Cmd/Ctrl-Click to center the pixel under the cursor.
Use the left and right arrow buttons to rotate in 15º increments, or enter a number in degrees (counter-clockwise) in the box between them.
By default, rotation is about the image center, but you can set a pivot point by Cmd/Ctrl-Shift-clicking the desired point.
Shift-clicking on the image calls an optional Python callback with continuous data-space coordinates (x, y including fractional pixel position).
Overlay help text is optional and only shown when you provide overlay_message.
Matplotlib integration
Once you've rotated and panned and stretched and zoomed you may want to save a plot, but the viewer doesn't handle plotting.
Fortunately, the widget has a plot_to_matplotlib() method that takes a matplotlib.axes.Axes instance:
fig, ax = plt.subplots()
widget.plot_to_matplotlib(ax)
Note: Rotating the axes makes the matplotlib tick labels useless, so they are hidden.
If you just want the contrast / bias / stretch, you can get a norm from the get_normalization() method:
norm = widget.get_normalization()
import matplotlib.pyplot as plt
plt.imshow(x, norm=norm)
Widget API
ViewerConfig
Using the ViewerConfig dataclass or passing its arguments to show() lets you set the initial configured state of the viewer.
pyviewarr.show(x, vmin=-10, vmax=10)
See example.
Marker coordinates API
Use widget.markers to supply marker positions as continuous image coordinates.
widget = pyviewarr.viewarr(x)
widget.markers = [(10.5, 20.25), (100.0, 42.0)]
Markers are rendered as fixed-size plus signs in screen space, and follow pan/zoom/rotation transforms.
Shift-click callback API
Use ViewerConfig.on_shift_click to receive continuous data-space click coordinates:
def on_shift_click(x: float, y: float) -> None:
print(f"Shift-click at x={x:.3f}, y={y:.3f}")
cfg = pyviewarr.ViewerConfig(
on_shift_click=on_shift_click,
overlay_message="Shift-click to report coordinates",
)
widget = pyviewarr.viewarr(x, viewer_config=cfg)
widget
For a demo that combines callbacks with marker updates, see shift-click callback demo.
Setting data
If you retain a reference to the widget, you can set its contents from a later cell (if you want).
widget = pyviewarr.show(x)
widget
Now you can change the live widget's contents by supplying a new array to set_array().
new_arr = np.random.randn(512, 512).astype(np.float32) * 100
widget.set_array(new_arr)
Development
Be sure to clone with git clone --recurse-submodules (or, if you cloned first and then read this, git submodule update --init --recursive to initialize an existing clone).
The frontend part of the widget (i.e. viewarr itself) is written in Rust with egui, requiring a Rust compiler toolchain for wasm32-unknown-unknown and the wasm-pack tool installed.
Install rust with rustup: https://rustup.rs/
Now that you have cargo, install wasm-pack with cargo install wasm-pack.
Using uv for development will automatically manage virtual environments and dependencies for you.
For live reloading in development:
export ANYWIDGET_HMR=1
Export this variable before starting JupyterLab so it will use hot module reloading.
uv run jupyter lab example.ipynb
Alternatively, create and manage your own virtual environment:
python -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"
The widget front-end code bundles it's JavaScript dependencies. After setting up Python, make sure to install these dependencies locally:
npm install
While developing, you can run the following in a separate terminal to automatically rebuild JavaScript as you make changes:
npm run dev
Open example.ipynb in JupyterLab, VS Code, or your favorite editor
to start developing. Changes made in js/ will be reflected
in the notebook.
To do a full build, use the project script:
npm run build:all
End-to-end tests (Galata + Playwright)
The widget has browser E2E tests using JupyterLab's Galata helpers.
First-time setup for browser binaries:
npm run test:e2e:install
Run E2E tests headless:
npm run test:e2e
Run E2E tests with a visible browser:
npm run test:e2e:headed
The test server uses tests/e2e/jupyter_server_config.py, which enables Galata's JupyterLab test hooks.
Releasing
Note that viewarr/ submodule changes will need to be committed and pushed first, then the submodule reference in this repository can be updated.
Release checklist:
- Update changelog entries and set
[project].versioninpyproject.tomlto the release version (e.g.0.3.2), then commit. - Create the Git tag/release for that version (e.g.
v0.3.2). - Immediately after release, bump
pyproject.tomlto the next development version (e.g.0.3.3dev) and commit.
GitHub releases are automatically pushed to PyPI by the workflow in .github/workflows/ci.yml.
Changelog
Unreleased (since v0.3.2)
pyviewarr changes
- Added
ViewerConfig.on_shift_clickPython callback to receive shift-click coordinates in data space (x,y) with fractional precision. - Refactored overlay text to generic
ViewerConfig.overlay_message(not callback-specific). - Removed default overlay text; overlay is now hidden unless
overlay_messageis provided. - Added tests covering shift-click callback wiring and
ViewerConfigJS serialization exclusions for Python-only fields. - Added a demonstration notebook:
notebooks/shift_click_callback_demo.ipynb. - Updated notebook callback logging example to use
ipywidgets.Outputfor reliable async callback output display. - Updated usage docs with shift-click callback example and notebook link.
- Updated bundled
viewarrsubmodule to include shift-click callback and overlay layout improvements. - Updated bundled
viewarrsubmodule to include diverging-mode colorbar limit textbox fixes.
Included viewarr changes
- Added shift-click callback events via
onClick(...)with continuous (fractional) data-space coordinates. - Added generic overlay message APIs:
getOverlayMessage(...)andsetOverlayMessage(...). - Added
overlayMessagesupport tosetViewerState(...). - Renamed overlay API from shift-click-specific names to generic names (
getOverlayMessage/setOverlayMessage,overlayMessagein state config). - Fixed diverging/symmetric colorbar limit editing/reporting behavior and
vmintextbox refresh when switching back to non-symmetric modes. - Removed default overlay text; overlay only renders when message text is supplied.
- Updated overlay placement to compute a live safe area between bottom overlays, avoiding overlap with hover coordinates and zoom controls while keeping the message centered in that gap.
v0.3.2
pyviewarr changes
- Updated bundled
viewarrsubmodule from3797ee7tocc78498.
Included viewarr changes
- Fixed diverging/symmetric colorbar limit behavior so
vmaxis the only editable limit, coerced positive, andvminis displayed as-vmaxin that mode. - Fixed state callback /
getValueRange()limit reporting in diverging/symmetric mode to reflect the effective displayed range.
v0.3.1
pyviewarr changes
- Added browser end-to-end testing with Playwright + JupyterLab Galata (
playwright.config.ts,tests/e2e/). - Added CI coverage for Playwright E2E tests in
.github/workflows/ci.yml. - Expanded development documentation for build/test workflows.
- Updated bundled
viewarrsubmodule from3d74f69to3797ee7.
Included viewarr changes
- Fixed Cmd/Ctrl-click centering coordinate mapping.
- Pinned wasm-bindgen stack to avoid
glow/js-sysCI build breakages. - Added/expanded viewer state APIs in JS/TS:
setViewerState(...)for partial bulk state updates.getZoom(...)/setZoom(...).setColormap(...)/setColormapReversed(...).- New
StretchModeandViewerStateConfigtypings.
- Improved colormap name handling/parsing with canonical names and aliases (
gray/grayscale/greyscale, etc.).
Metadata
Release files for pyviewarr 0.3.5
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 |
|---|---|---|---|---|
| pyviewarr-0.3.5.tar.gz | 2.0 MB | With provenance | Details for pyviewarr-0.3.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyviewarr-0.3.5-py3-none-any.whl | Python 3 | none | any | Details for pyviewarr-0.3.5-py3-none-any.whl |
Total release size: 4.0 MB
Release files / pyviewarr-0.3.5.tar.gz
| Download URL | pyviewarr-0.3.5.tar.gz |
|---|---|
| Size | 2.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d9ac97628c9633eb32b4e65b43aefc44691abf5a2e27e2a49ce92dc5d2f46528
|
|
BLAKE2b-256 checksum How to use checksums |
b9f722b51633d1c72198a9e011a534172d21759763e10ea82e4b539af450ed4e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2026.
Transparency logRelease files / pyviewarr-0.3.5-py3-none-any.whl
| Download URL | pyviewarr-0.3.5-py3-none-any.whl |
|---|---|
| Size | 2.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6c2032f88c6c3220c3c36518bc11cc401b5e5fe080da78e399616e61741fd9f7
|
|
BLAKE2b-256 checksum How to use checksums |
5b1c21bcbddfc1cb4c2cda7efbd2a6835c626bd4679950b82849c83513e48db9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2026.
Transparency logSecurity for pyviewarr 0.3.5
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for pyviewarr-0.3.5.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2026.
Transparency logA 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.