Wetlands
Wetlands lets a Python application run functions and external commands in separate Pixi environments.
This is useful when one application needs libraries whose dependencies cannot be installed together. Wetlands creates the environments, keeps worker processes ready for repeated calls, transfers ordinary Python values between the application and workers, and supervises commands and services installed in an environment.
Wetlands is intended for code you trust. Environments prevent dependency conflicts, but they do not restrict what code can access on your computer.
Install
pip install wetlands
Wetlands transfers NumPy array data between the application and workers through operating-system shared memory automatically. Install the optional host-side NumPy support when arrays cross the worker boundary:
pip install "wetlands[shared-memory]"
Also include NumPy in each managed worker environment that receives or returns arrays. Your code uses ordinary, independently owned arrays; it never manages shared-memory handles directly. See NumPy arrays and shared-memory transport for the complete transfer model.
Run a task
from wetlands import EnvironmentManager, EnvironmentSpec
with EnvironmentManager(root="wetlands") as manager:
environment = manager.provision(
"first-example",
EnvironmentSpec(python="3.12.*"),
).wait_for()
with environment.start() as workers:
result = workers.execute_import(
"builtins:sum",
args=([20, 22],),
)
print(result) # 42
The first run may download Pixi and Python packages and can take several minutes.
Continue with the first-task tutorial or browse the complete documentation. Existing Wetlands 1 users should read the migration guide.
Development
Install the development environment:
uv sync --frozen --group dev --extra shared-memory
Run the fast tests and static checks:
uv run --extra shared-memory pytest -m "not integration and not compat and not manual"
uv run ruff check
uv run ruff format --check
uv run mypy src/wetlands
Start with the contributor setup and validation guide. The architecture guide explains the runtime design. Maintainers should follow RELEASING.md when publishing a release.
Wetlands is licensed under the MIT License. Read the security policy before executing third-party worker code, managed commands, or post-install commands.
1 maintainer
Metadata
1 maintainer
Release files for wetlands 2.6.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| wetlands-2.6.0.tar.gz | 361.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| wetlands-2.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 509.8 kB
Release files / wetlands-2.6.0.tar.gz
| Download URL | wetlands-2.6.0.tar.gz |
|---|---|
| Size | 361.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4db1abd22cfe6a2e64dfbfaa831a86df368ab15a2a63490fdfd1a32e89da4ab7
|
|
BLAKE2b-256 checksum How to use checksums |
8beb2dbbbae3e140e17de67acd94a291d16d5f076765f05b3908454d53e02985
|
| 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 5, 2026.
Transparency logRelease files / wetlands-2.6.0-py3-none-any.whl
| Download URL | wetlands-2.6.0-py3-none-any.whl |
|---|---|
| Size | 148.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9afcb38d70ddeb8123d52433c169d5ae2e924901ce7e2b501de36b733730d425
|
|
BLAKE2b-256 checksum How to use checksums |
1ebf5a29b16b158cf2100d8218e24365fe0c16706a4b106bbc06de41a41b614b
|
| 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 5, 2026.
Transparency log
