This release is a pre-release and may not be stable for production use.
UniEnv
UniEnv is a Python framework for building robot environments and robot data pipelines on top of a shared set of abstractions.
Documentation: https://unienvorg.github.io/UniEnv/
It gives you:
- a common environment interface for simulation and real-robot control
- a functional environment variant for explicit state passing
- backend-aware spaces, wrappers, and transformations
- world and node composition utilities for multi-component environments
- lightweight remote execution (RPC over TCP, Unix sockets or WebSocket) with observer streams
- replay buffers, storages, samplers, and dataset adapters for offline data workflows
The project is designed around one idea: environment code and dataset code should not have to be rewritten every time the simulator, robot, or tensor library changes.
What Is In The Package
unienv_interface: environments, worlds, nodes, spaces, wrappers, and transformationsunienv_data: batches, replay buffers, storage backends, samplers, and dataset integrations- backend portability through XBArray and DLPack-based conversion paths
Installation
Install the base package:
pip install unienv
Install optional extras when needed:
pip install "unienv[gymnasium,video]"
Some integrations and storage backends rely on their own ecosystem packages such as pyarrow, h5py, datasets, huggingface_hub, torch, or jax. Install the ones that match the features you plan to use.
Quick Example
The example below shows the core building blocks without depending on a specific simulator:
import numpy as np
from unienv_interface.backends.numpy import NumpyComputeBackend
from unienv_interface.space.spaces import BoxSpace, DictSpace
from unienv_interface.transformations import RescaleTransformation
from unienv_data.replay_buffer import ReplayBuffer
from unienv_data.storages.parquet import ParquetStorage
backend = NumpyComputeBackend
transition_space = DictSpace(
backend,
{
"obs": BoxSpace(backend, 0.0, 1.0, np.float32, shape=(4,)),
"action": BoxSpace(backend, -1.0, 1.0, np.float32, shape=(2,)),
"reward": BoxSpace(backend, -np.inf, np.inf, np.float32, shape=()),
},
)
action_transform = RescaleTransformation(new_low=0.0, new_high=1.0)
normalized_action_space = action_transform.get_target_space_from_source(
transition_space["action"]
)
buffer = ReplayBuffer.create(
ParquetStorage,
transition_space,
cache_path="cache/demo_buffer",
capacity=10_000,
)
print(normalized_action_space)
print(buffer.single_space)
For online logging, append one sample at a time with ReplayBuffer.append(value) and close each segment with mark_segment_end(). Segment visibility depends on the storage backend: legacy storages may expose writes immediately, while VideoStorage finalizes its active segment before it becomes readable.
In practice, you would pair these components with your own Env, FuncEnv, World, or WorldNode implementations, then add wrappers and storage backends as needed.
Documentation
Documentation: https://unienvorg.github.io/UniEnv/
Start with:
docs/getting-started.mdfor installation and the package mapdocs/concepts/for the core abstractionsdocs/guides/for wrappers, replay buffers, and dataset integrationsdocs/guides/remote-execution.mdfor remote environments, nodes, and worlds (pip install 'unienv[network]')
Development
For local development:
git clone https://github.com/UniEnvOrg/UniEnv
cd UniEnv/UniEnvPy
pip install -e .[dev,gymnasium,video]
pytest
If you want to exercise optional backends or integrations during development, install their matching dependencies explicitly before running the relevant tests.
Cite
If you use UniEnv in research, cite:
@software{cao_unienv,
author = {Yunhao Cao AND Cory Fan AND Meryl Zhang AND Sabrina Liu AND Kuan Fang},
title = {{UniEnv: Unifying Robot Environments and Data APIs}},
year = {2025},
month = oct,
url = {https://github.com/UniEnvOrg/UniEnv},
license = {MIT}
}
Acknowledgements
UniEnv is influenced by Gymnasium and OpenAI Gym, and builds on ideas from the Array API Standard and DLPack.
Metadata
Release files for unienv 0.0.1b16
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 |
|---|---|---|---|---|
| unienv-0.0.1b16.tar.gz | 344.2 kB | With provenance | Details for unienv-0.0.1b16.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| unienv-0.0.1b16-py3-none-any.whl | Python 3 | none | any | Details for unienv-0.0.1b16-py3-none-any.whl |
Total release size: 774.0 kB
Release files / unienv-0.0.1b16.tar.gz
| Download URL | unienv-0.0.1b16.tar.gz |
|---|---|
| Size | 344.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1522934947caef43a94ea87f399965d09942ec42374dbe91343216e3b1172738
|
|
BLAKE2b-256 checksum How to use checksums |
43a09804f9bcb40a77214b54f3ded118da142d3dc49a349ac17fcc5ee5555e6f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 17, 2026.
Transparency logRelease files / unienv-0.0.1b16-py3-none-any.whl
| Download URL | unienv-0.0.1b16-py3-none-any.whl |
|---|---|
| Size | 429.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
02ec02448f541b7759acc130ea2547abb6b2f2a3611e01a8b58ed0af9f3925f7
|
|
BLAKE2b-256 checksum How to use checksums |
0dcfdf910ac10c51f216404f9b097edb96d4888d9d81f88cb966923b5a851bb9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 17, 2026.
Transparency logSecurity for unienv 0.0.1b16
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 unienv-0.0.1b16.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 Oct 17, 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.