-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider publishing the Rust code in this repo as a crate #178
Comments
Would it be possible to use a git dependency on this repository? From a Cargo dependency perspective I think that should work, and it would likely entail exporting a few things, but that should be ok |
A git dependency would be a bit tough for our use-case since we will be providing this to end users and would prefer to always be pinned to an explicit release. One of my more python savvy teammates suggested using |
For the pinning, would tags perhaps work out? Either that or specific revisions (or having a I'm not 100% sure what your build system and integration would look like however, so I could easily be missing something. |
Apologies for the lack of reply, just getting back around to this as some other work took me away from it. We ended up combining your suggestion of a GH dependency + the tag targeting with the (nightly) artifact dependencies cargo feature to get something working. Would still like to see the crates published to crates.io to keep things in step with the rest of the ecosystem (ex: js-component-bindgen) and to enable publishing other crates that rely on wasmtime-py. |
We have a need to generate Python component bindings from a Typescript application. I've been able to do that by building the Rust code in this repository and using
jco
to create TS bindings for it (see below). But that requires vendoring the Rust code or generated WASM binary in our application. If the core Rust code in this repo were published as a crate we could use Cargo to handle the dependency management with less worries about keeping the wasmtime-py module up to date.The text was updated successfully, but these errors were encountered: