Releases

Wasmtime Python Bindings Version 43.0.0 Arrives on PyPI for WebAssembly Integration

Fastly once saw a 163% jump in requests-per-second on Wasmtime; v43.0.0 of the Python bindings landed on PyPI, continuing the runtime's unbroken monthly release streak.

Sam Ortega2 min read
Published
Listen to this article0:00 min
Share this article:
Wasmtime Python Bindings Version 43.0.0 Arrives on PyPI for WebAssembly Integration
Source: wasmlabs.dev
This article contains affiliate links, marked with a blue dot. We may earn a small commission at no extra cost to you.

When Fastly switched WebAssembly engines in March 2022, it measured up to a 163% increase in requests-per-second. The engine it moved to was Wasmtime, and on March 31, 2026, the 43rd consecutive monthly major release of its Python bindings landed on PyPI.

That unbroken cadence has run since the Bytecode Alliance declared Wasmtime 1.0 production-ready on September 20, 2022. Version 43.0.0 of the wasmtime-py package brings the latest upstream runtime changes to Python integrators without requiring a native Rust toolchain: pre-built wheels cover Python 3.9 and later on 64-bit Windows, macOS, and Linux, targeting both x86_64 and arm64 architectures. The package is also available on conda-forge.

The production case for Wasmtime extends well beyond Fastly. Shopify has run the engine since July 2021 and reported roughly a 50% average execution performance improvement. Microsoft Azure is also a noted production user. Those deployments help explain why the wasmtime GitHub repository has accumulated over 17,700 stars and approximately 1,600 forks as of early 2026, with the PyPI package crossing 3.5 million total downloads.

On the upstream side, recent Wasmtime releases included support for the WASIp3 snapshot at version 0.3.0-rc-2026-03-15, alongside fixes to async stream and future read/write cancellation, Cranelift compiler timing infrastructure, and cooperative component-model async task management. Python developers embedding Wasmtime for sandboxing, plugin systems, or Wasm-based business logic will find the upgrade path for bugfixes and new host interface features runs directly through keeping wasmtime-py current.

AI-generated illustration
AI-generated illustration

One operational detail worth flagging: because every package in a Python environment must agree on a single version of wasmtime-py, dependency files that pin an upper bound on the major version need to be bumped promptly when a new release ships. The Wasmtime project recommends automating that with Dependabot or Renovate rather than waiting for a conflict to surface in CI. Breaking changes between monthly major versions are possible, so integration tests against the new release in a staging environment are the practical safety net before rolling to production.

For teams that cannot absorb monthly upgrades, the LTS track provides the alternative. The v36.0.0 LTS release, dated August 20, 2025, carries support through August 20, 2027, a two-year security maintenance window. Wasmtime maintains two active LTS releases alongside up to two normal releases at any given time.

The wasmtime-py package is a Bytecode Alliance project, developed under the governance of the 501(c)(6) nonprofit founded in November 2019 by Mozilla, Fastly, Intel, and Red Hat, now counting roughly 30 member organizations including Amazon, Arm, Google, Microsoft, and VMWare. Wasmtime holds the distinction of being the Alliance's first Core Project, its highest governance tier, and exposes bindings for C/C++, .NET, and Go in addition to Python and its native Rust API. The project's contributors are primarily Rust programmers, which makes Python-idiomatic improvements submitted via pull request particularly welcome from the broader community.

Know something we missed? Have a correction or additional information?

Submit a Tip

Discussion

More Rust Programming News