You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: component-model/src/language-support/python.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -97,8 +97,8 @@ Component built successfully
97
97
98
98
## Running components from Python Applications
99
99
100
-
Wasm components can also be invoked from Python applications. This walks through using tooling
101
-
to call the [`app.wasm` component from the examples](../../examples/example-host/add.wasm).
100
+
Wasm components can also be invoked from Python applications. This section walks through using tooling
101
+
to call the [pre-built `app.wasm` component][add-wasm] in the examples.
102
102
103
103
> `wasmtime-py` is only able to run components built with `componentize-py` when the `--stub-wasi` option is used at build time. This is because `wasmtime-py` does not yet support [resources](../design/wit.md#resources), and `componentize-py` by default generates components which use resources from the `wasi:cli` world. See [this example](https://github.com/bytecodealliance/componentize-py/tree/main/examples/sandbox) of using the `--stub-wasi` option to generate a `wasmtime-py`-compatible component.
0 commit comments