USD-QtPy
Python Qt components for building custom USD tools.
How to use?
The Qt components can be embedded in your own Qt interfaces and usually have
a stage entrypoint that you should pass a pxr.Usd.Stage instance.
However, a simple example Editor UI is also available to run standalone.
If you have the usd_qtpy package you can for example run it like:
python -m usd_qtpy "/path/to/file.usd"
Want to try it within your running Python session it should be as trivial to do:
from pxr import Usd
from qtpy import QtWidgets
from usd_qtpy.editor import EditorWindow
filepath = "/path/to/file.usd"
stage = Usd.Stage.Open(filepath)
app = QtWidgets.QApplication()
dialog = EditorWindow(stage=stage)
dialog.resize(600, 600)
dialog.show()
app.exec_()
Or if you have a running QApplication instance (e.g. when inside Maya):
from pxr import Usd
from usd_qtpy.editor import EditorWindow
filepath = "/path/to/file.usd"
stage = Usd.Stage.Open(filepath)
dialog = EditorWindow(stage=stage)
dialog.resize(600, 600)
dialog.show()
Why not Luma Picture's usd-qt?
Unlike Luma Pictures's usd-qt this repository tries to be easily
redistributable by avoiding the need for extra C++ dependencies and solely
use the USD Python API. This will keep the build matrix simpler but does mean
the repository is not - by design - built for highly optimized large scale
applications. Nonetheless, the intent is still to be able to carry average VFX
scenes for debugging.
install
from pip
python -m pip install usd-qtpy
from repo
python -m pip install git+https://github.com/BigRoy/usd-qtpy.git@main
Dependencies
The Viewer utilities are basically using usdviewq which may or may not
be included in your build. This also requires PyOpenGL. However, the other
tools do not and are intended to rely solely on USD core and Qt itself.
- qtpy
- usd-core (when not using your own usd builds, install with
[usd]) - PyOpenGL (needed for usd viewport, install with
[usdview]; you will still need use a customusdbuild yourself forpxr.Usdviewqdependency)
Metadata
Release files for usd-qtpy 0.0.1
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 |
|---|---|---|---|---|
| usd-qtpy-0.0.1.tar.gz | 33.8 kB | Without provenance | Details for usd-qtpy-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| usd_qtpy-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for usd_qtpy-0.0.1-py3-none-any.whl |
Total release size: 73.3 kB
Release files / usd-qtpy-0.0.1.tar.gz
| Download URL | usd-qtpy-0.0.1.tar.gz |
|---|---|
| Size | 33.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
11a8bb1fdf3a93e027003d412d4a3f45d574db1502c6389f417d82670e2b05dd
|
|
BLAKE2b-256 checksum How to use checksums |
fd2ba24901045f571b067b9aff87ab9f6082a0d62912e75421ae7d0e500ec861
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.18
|
Release files / usd_qtpy-0.0.1-py3-none-any.whl
| Download URL | usd_qtpy-0.0.1-py3-none-any.whl |
|---|---|
| Size | 39.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
adb825fd791b29f7e947145840a339d2b0115fa520adf4158af10ff3c4e37589
|
|
BLAKE2b-256 checksum How to use checksums |
d4f93152e1857e829f718aa04d34876503c2044e5df9dd8688cd28a4a0b65513
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.18
|
Security for usd-qtpy 0.0.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.