Holoscan Camera Python support
Holoscan Camera exposes native camera capture operators to Holoscan SDK 5 Python graphs. Capture, buffer ownership, and device lifecycle remain in C++. Python applications use the SDK's typed image payloads and tensor APIs.
Import operators from holoscan_camera.operators. The SDK also discovers the
package through the holoscan.camera alias. A Python operator facade loads its
backend and resolves a Core registry proxy; it does not implement capture.
Wheel builds configure facades and typing declarations for all three backends.
Usability depends on the wheel's native extensions, host hardware, and runtime
libraries. An advertised name or .pyi declaration is not a capability check.
SIPLCaptureService and its related value types are bound directly by _sipl.
The default wheel build includes V4L2. Running capture requires a compatible camera, the matching Holoscan Core CUDA 13 package, and the platform's native runtime libraries. Wheels do not bundle camera drivers or the system CUDA runtime. Install the artifact qualified for your target platform.
Source builds require CMake 4+, a C++20 toolchain, CPython 3.12+, and a matching
Holoscan SDK development installation with Python support and its exported
Python build helpers. Build and application instructions are provided in the
source distribution's python/README.md and application directories.
The ARM64 wheel includes V4L2 and separate R39 SIPL v2 and Argus extensions.
V4L2 remains usable on SBSA/DGX Spark and R38 without loading those backends.
R39 SIPL requires supported Orin/Thor hardware; R39 Argus requires Orin.
The x86_64 wheel supports V4L2. Unsupported backend imports may fail; wildcard
imports request all backends. Attribute probes such as hasattr() and
inspect.getmembers() can also request a backend and propagate ImportError.
R38 SIPL is not supported by the wheel.
Metadata
Release files for holoscan-camera-cu13 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| holoscan_camera_cu13-1.0.0-cp312-abi3-manylinux_2_39_x86_64.whl | CPython 3.12 | abi3 | Linux glibc 2.39+ x86-64 | Details for holoscan_camera_cu13-1.0.0-cp312-abi3-manylinux_2_39_x86_64.whl |
| holoscan_camera_cu13-1.0.0-cp312-abi3-manylinux_2_39_aarch64.whl | CPython 3.12 | abi3 | Linux glibc 2.39+ ARM64 | Details for holoscan_camera_cu13-1.0.0-cp312-abi3-manylinux_2_39_aarch64.whl |
Total release size: 813.3 kB
Release files / holoscan_camera_cu13-1.0.0-cp312-abi3-manylinux_2_39_x86_64.whl
| Download URL | holoscan_camera_cu13-1.0.0-cp312-abi3-manylinux_2_39_x86_64.whl |
|---|---|
| Size | 128.7 kB |
| Tags | CPython 3.12 Linux glibc 2.39+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
e0d7b021c1d4934b0e207038f5370d9c3106f41fcd7022e036abdda2a33cadf3
|
|
BLAKE2b-256 checksum How to use checksums |
2d50fe46c70780479b8a35da8293a8cec7afcd2cd87e6826d6fcd089a80f5aa8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Release files / holoscan_camera_cu13-1.0.0-cp312-abi3-manylinux_2_39_aarch64.whl
| Download URL | holoscan_camera_cu13-1.0.0-cp312-abi3-manylinux_2_39_aarch64.whl |
|---|---|
| Size | 684.7 kB |
| Tags | CPython 3.12 Linux glibc 2.39+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
e205f48019dc21d336482cb427b57693a7be3b0aa2d5b51945ba1cc719ce2495
|
|
BLAKE2b-256 checksum How to use checksums |
4ce18befa4f35a1d9f109192aa524904552460fb0d4873c63d1d5e98060ca5c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Security for holoscan-camera-cu13 1.0.0
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.