ovui-widgets-all
Meta-package for installing the complete ovui-widgets stack: the USD Viewer
application, common services, Stage Browser, Layers panel, Content Browser,
Property Inspector, Viewport, and the common plus OpenUSD
data-adapter packages. It requests the OpenUSD adapter's standalone extra so
a clean aggregate installation also receives the supported usd-core runtime.
Python 3.12 and 3.13 only: that extra pins usd-core==25.11, which has no wheel
for Python 3.14 or 3.15, so this package cannot be installed there. On Python
3.14 and 3.15 install the component packages and either the OVStage provider
(ovui-data-adapters-ovstage) or the plain ovui-data-adapters-openusd with a
matching pxr from the environment.
Install this package when a project wants the full scene-tooling surface rather
than one widget distribution at a time. Kit and custom-USD environments that
must retain their matching pxr runtime should install the component packages
and plain ovui-data-adapters-openusd instead of this standalone aggregate.
Metadata
Release files for ovui-widgets-all 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ovui_widgets_all-0.3.1-py3-none-any.whl | Python 3 | none | any | Details for ovui_widgets_all-0.3.1-py3-none-any.whl |
Release files / ovui_widgets_all-0.3.1-py3-none-any.whl
| Download URL | ovui_widgets_all-0.3.1-py3-none-any.whl |
|---|---|
| Size | 6.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cc74779d6b6b9158180e1b8599582ec6232742800075a879978c878d53edc966
|
|
BLAKE2b-256 checksum How to use checksums |
9606d27d406fd1b62d71f676c677522941443a0ed3720325a6ddf8820b4212b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Security for ovui-widgets-all 0.3.1
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.
