Fix Python Tutorial

Open
#348 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
python, wasm
Domain
documentation

Research direction

Start with the “Running components from Python Applications” section at language-support/building-a-simple-component/python.html and reproduce the documented wasmtime.bindgen command with the current package. Read the referenced wasmtime-py issues #309 and #310 to establish the supported status, then update the tutorial with a verified workflow or a clear availability note and confirm the example no longer misleads users.

Written by the indexing model from the issue text.

Description

bug lang/python

Hello,

I encountered an issue while following the "Running components from Python Applications" section in the documentation.

The documentation currently instructs users to install wasmtime and then run:
python3 -m wasmtime.bindgen add.wasm --out-dir add
However, with the current wasmtime package, this fails with:
No module named wasmtime.bindgen

It looks like wasmtime.bindgen was removed from wasmtime-py in bytecodealliance/wasmtime-py#310. The PR says that wasmtime.bindgen was removed in favor of component support in the C API, and that reimplementing bindgen for components is deferred to future work in bytecodealliance/wasmtime-py#309.

So I think this section of the documentation may now be outdated.

Expected behavior

The tutorial should provide a working way to run the add.wasm component from a Python host application, or mention that this workflow is no longer available with current versions of wasmtime-py.

Actual behavior

The documented command fails because wasmtime.bindgen is no longer available.

Environment

  • Python 3.12.3 via pyenv
  • wasmtime: latest version installed by pip install wasmtime
  • OS: Ubuntu 24.04.1 LTS (Noble Numbat)
  • Architecture: x86_64
Dominant language
Rust
Stars
137
Forks
88
Avg merge
5d 12h
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bytecodealliance/component-docs

All issues in bytecodealliance/component-docs

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.