(kit-python-package-main-doc)=
Kit Python Package
Kit is published as a Python (PIP, wheel) package. This means that you can use Kit as a Python library in your Python projects.
It can be found PyPI index. But it is a placeholder package, to install Kit from PyPI you need pass an extra index URL to pip:
pip install omniverse-kit --extra-index-url https://pypi.nvidia.com
Getting Started
python -m venv myenv
myenv\Scripts\activate
pip install omniverse-kit --extra-index-url https://pypi.nvidia.com
python -m omni.kit_app
In this example we create a new virtual environment, activate it, install Kit into it as python package, and run Kit. It will start in the same way as if it was started from the kit.exe, but instead your python is used.
KitApp Example
The omni.kit_app module provides an initial bootstrapping and KitApp class, which is a Pythonic way to start Kit. It is a thin wrapper around the kit.exe command line interface, and it provides a way to start Kit from Python, to pass command line arguments to it, to control the basic update loop:
:language: py
In this example we startup Kit asking it to enable omni.ui extension. Use it to build a simple UI window. After that we keep app update loop running until app is signaled to exit.
That will only work if among enabled extension is omni.kit.loop (or similar) which implements the main update loop interface (omni::kit::IRunLoopRunner). Otherwise Kit will exit.
The from omni.kit_app import KitApp import must be the first of omniverse imports, it sets up the environment (loads Carbonite, adds library and python paths).
Typically extensions subscribe to update loop events (like render UI every frame, process new input events, etc). However, for some applications it might be useful to have a full control over the update loop. To call explicit API of various extensions, rather than rely on their event-based API:
:language: py
In this example we startup Kit asking it to enable omni.usd extension. After that extension is available (added to sys.path, startup was called) and we can use it in our Python code.
EULA
On the first import of omni.kit_app module, it will ask you to accept the EULA. This is a one-time operation, if accepted, it will not ask again. An alternative way to accept the EULA is to set the environment variable OMNI_KIT_ACCEPT_EULA to yes.
Editable Mode
You can install Kit python package in editable mode, which means that you can modify the source code and see the changes immediately. This is useful for development and debugging.
Assuming you've built Kit from source:
pip install -e [path to kit source]/_build/packages/python/omniverse-kit
Metadata
Release files for omniverse-kit 109.0.0.247772
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| omniverse_kit-109.0.0.247772.tar.gz | 2.0 kB | Details |
Release files / omniverse_kit-109.0.0.247772.tar.gz
| Download URL | omniverse_kit-109.0.0.247772.tar.gz |
|---|---|
| Size | 2.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8615916e4f2a9bb23925030da43a94571db60b3a9169ebe8883399c9363fcbd4
|
|
BLAKE2b-256 checksum How to use checksums |
f055e67360c067ff5ba8affaff70c94502702031bd23e05c9bf832a5e9dc1c6e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.10.19
|
