--- orphan: false --- # What's new in v0.4.1 ```{versionadded} v0.4.1 ``` v0.4.1 (2026-10-13) fixes the packaging and its documentation. No library code changed; everything in the [v0.4.0 notes](v0.4.0.md) still holds. ## Fixed - **`pip install maddening[all]` and `maddening[dev]` install from wheels again.** In 0.4.0 and earlier, `all` included PyGObject, the Python bindings the `streaming` extra uses. PyPI publishes PyGObject as source only, so pip had to compile it, and the build stopped with `Dependency "cairo" not found` on a machine without the cairo and GObject-introspection development headers. `dev` includes `all`, so the development install failed the same way. - `all` is now every feature extra except `usd` and `streaming`, plus the RunPod and Lambda cloud providers. - `streaming` still installs PyGObject. It also needs GStreamer and its WebRTC plugins, which come from your system's package manager, not from pip: see [Streaming prerequisites](../user_guide/installation.md#streaming-prerequisites). - CI now resolves `all` and `dev` from wheels alone on every push, so a dependency that needs a build cannot slip back into them. - **On 0.4.0 or earlier,** name the extras of `all` except `streaming` instead: ```bash pip install "maddening[viz,terminal,network,api,surrogates,viz3d,gpu-viz,compression,cloud]" ``` - **A `pip install -e ".[dev]"` checkout can run the tests again.** Since 0.4.0 `tests/conftest.py` imports hypothesis, which `dev` did not install; nor did it carry the starlette floor the API tests need or the build backend the packaging test uses. `dev` now includes the `verify` extra and both. - **The installation guide lists every extra.** `verify` (hypothesis, which `maddening.testing` needs to verify your own nodes) was documented only in the developer guide; `dev`, `ci` and `sbom` now have a section of their own. ## Known anomalies - `MADD-ANO-296` records this defect, resolved in 0.4.1. The registry's other entries are unchanged from 0.4.0.