componentize-py
componentize-py copied to clipboard
bytecodealliance
I'd like to execute code using the sandbox example, but am running into an issue. I want to allow exec'd code to import packages, but if I don't import packages...
I think this is actually a bug but it may not be one that idiomatic wit files would trigger so it may not be an important issue but I'll post...
Some packages (in particular, `aiohttp`) require CPython to be built with zlib enabled. I believe this is [known work](https://bytecodealliance.zulipchat.com/#narrow/stream/394175-SIG-Guest-Languages/topic/Compile.20python.20binary.20packages.20for.20componentize-py/near/418155228) but I wanted to create a tracking issue here for it....
## Error I ran into the following error: ```sh $ componentize-py --wit-path add.wit --world example componentize example -o add.wasm Traceback (most recent call last): File "/opt/homebrew/bin/componentize-py", line 8, in sys.exit(script())...
In addition to running the test suite, we should dump the app code and generated bindings in a directory and run MyPy on them, asserting that no errors are found....
This should include a `CONTRIBUTING.md` file, plus an `ARCHITECTURE.md` describing the high-level architecture of the project. In addition, each source file needs doc and implementation comments.
The current Python binding generator predates the concept of WIT packages, and we need to update it. Otherwise, importing or exporting two interfaces with the same name but different packages...
This would dramatically reduce binary sizes in cases where the host can provide these libraries.
Currently, if Python code passes the wrong number or types of parameters to the host, or returns a result of an unexpected type, `componentize-py` generally reacts by panicking and trapping....
Currently, `componentize-py` generates no code for type aliases; instead, it just uses the dealiased types directly. Instead, we should generate assignment expressions for each alias and use the alias in...