Skip to content

Conversation

@alexcrichton
Copy link
Member

This fixes a typo in the bindings generation script which set the
`_fields` field rather than `_fields_`
@alexcrichton
Copy link
Member Author

Missing pieces:

  • Updated README
  • Delete wasmtime.bindgen or otherwise figure out what to do with it
  • Optimizations (the C API for components is pretty slow for passing data)
  • More thorough tests for variants-of-variants with varieties of Python types

I probably won't get to all of these before merging.

@alexcrichton alexcrichton marked this pull request as ready for review November 5, 2025 21:10
@alexcrichton
Copy link
Member Author

I'm going to do follow-ups for more items here.

@alexcrichton alexcrichton merged commit 0513ef7 into bytecodealliance:main Nov 5, 2025
12 checks passed
@alexcrichton alexcrichton deleted the components branch November 5, 2025 21:19
alexcrichton added a commit to alexcrichton/wasmtime-py that referenced this pull request Nov 5, 2025
This commit deletes two nice-to-have but difficult-to-maintain modules
in this repository. Specifically:

* The `wasmtime.loader` module is deleted as it was a proof-of-concept
  but doesn't map well to Python and Wasmtime. For example bytecodealliance#302 shows
  how destruction of Python modules isn't handled correctly. In general
  it's a "cute" implementation but isn't too too useful and doesn't map
  well to how Wasm is embedded in many contexts. I'm deleting this to
  reduce maintenance burden on this repository. It would be ok to
  reimplement in the future but it would likely require someone with
  more Python knowledge than I.

* The `wasmtime.bindgen` module is deleted in favor of component support
  in bytecodealliance#308. This module still makes sense to have but it would need a
  ground-up rewrite to work with component types rather than component
  definitions. This is deferred to future work in bytecodealliance#309 and in the
  meantime it's removed to avoid any confusion about what should be used
  and what shouldn't.

Closes bytecodealliance#105
Closes bytecodealliance#106
Closes bytecodealliance#107
Closes bytecodealliance#108
Closes bytecodealliance#109
Closes bytecodealliance#119
Closes bytecodealliance#143
Closes bytecodealliance#178
Closes bytecodealliance#181
Closes bytecodealliance#197
Closes bytecodealliance#202
Closes bytecodealliance#218
Closes bytecodealliance#245
Closes bytecodealliance#282
Closes bytecodealliance#302
alexcrichton added a commit that referenced this pull request Nov 5, 2025
* Delete `wasmtime.loader` and `wasmtime.bindgen`

This commit deletes two nice-to-have but difficult-to-maintain modules
in this repository. Specifically:

* The `wasmtime.loader` module is deleted as it was a proof-of-concept
  but doesn't map well to Python and Wasmtime. For example #302 shows
  how destruction of Python modules isn't handled correctly. In general
  it's a "cute" implementation but isn't too too useful and doesn't map
  well to how Wasm is embedded in many contexts. I'm deleting this to
  reduce maintenance burden on this repository. It would be ok to
  reimplement in the future but it would likely require someone with
  more Python knowledge than I.

* The `wasmtime.bindgen` module is deleted in favor of component support
  in #308. This module still makes sense to have but it would need a
  ground-up rewrite to work with component types rather than component
  definitions. This is deferred to future work in #309 and in the
  meantime it's removed to avoid any confusion about what should be used
  and what shouldn't.

Closes #105
Closes #106
Closes #107
Closes #108
Closes #109
Closes #119
Closes #143
Closes #178
Closes #181
Closes #197
Closes #202
Closes #218
Closes #245
Closes #282
Closes #302

* Remove some more metadata

* Remove build-rust build config
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant