Files
Mujoco_WASM/python
Sam Haves 723b8b1ea6 Introduce explicit VFS in Python MjVfs
This change introduces MjVFS, an explicit object to mirror the C mjVFS. This is meant to replace the MjSpec.assets dict. This latter while convenient guides users towards harmful authoring patterns with respect to data duplication and spec attachment workflows. Making VFS management explicit should encourage better memory usage and allow us to make better compile time optimizations.

From this change, `spec.assets` is deprecated. However we will temporarily support backwards compatibility due to the wide spread usage. An error will be thrown if calling code tries to use a spec that uses both the assets dict and the new MjVfs.

PiperOrigin-RevId: 908772050
Change-Id: I77c6d0369307fc300c954768fed17401261e18da
2026-05-01 09:34:17 -07:00
..
2024-07-01 12:05:50 -07:00
2024-12-09 21:10:50 -08:00

MuJoCo Python Bindings

PyPI Python Version PyPI version

This package is the canonical Python bindings for the MuJoCo physics engine. These bindings are developed and maintained by Google DeepMind, and is kept up-to-date with the latest developments in MuJoCo itself.

The mujoco package provides direct access to raw MuJoCo C API functions, structs, constants, and enumerations. Structs are provided as Python classes, with Pythonic initialization and deletion semantics.

It is not the aim of this package to provide fully fledged scene/environment/game authoring API, as there are already a number of existing packages that do this well. However, this package does provide a number of lower-level components outside of MuJoCo itself that are likely to be useful to most users who access MuJoCo through Python. For example, the egl, glfw, and osmesa subpackages contain utilities for setting up OpenGL rendering contexts.

Installation

The recommended way to install this package is via PyPI:

pip install mujoco

A copy of the MuJoCo library is provided as part of the package and does not need to be downloaded or installed separately.

Source

IMPORTANT: Building from source is only necessary if you are modifying the Python bindings (or are trying to run on exceptionally old Linux systems). If that's not the case, then we recommend installing the prebuilt binaries from PyPI.

If you need to build the Python bindings from source, please consult the documentation.

Usage

Once installed, the package can be imported via import mujoco. Please consult our documentation for further detail on the package's API.

We recommend going through the tutorial notebook which covers the basics of MuJoCo using Python: Open In Colab

Versioning

The major.minor.micro portion of the version number matches the version of MuJoCo that the bindings provide. Optionally, if we release updates to the Python bindings themselves that target the same version of MuJoCo, a .postN suffix is added, for example 2.1.2.post2 represents the second update to the bindings for MuJoCo 2.1.2.

License and Disclaimer

Copyright 2022 DeepMind Technologies Limited

MuJoCo and its Python bindings are licensed under the Apache License, Version 2.0. You may obtain a copy of the License at https://www.apache.org/licenses/LICENSE-2.0.

This is not an officially supported Google product.