-
Notifications
You must be signed in to change notification settings - Fork 22
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
Build WASM wheel #91
Build WASM wheel #91
Conversation
friendly ping to @davidbrochart or @DerThorsten for review, thanks! |
Sorry for the late answer @kafonek, I think Thorsten is the best person to review this. |
looks good to me, but disclaimer: I know nothing about rust |
Maybe @Waidhoferj wants to have a look too? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! I'm excited to see Ypy in the browser!
Thanks all, thanks for merging @Waidhoferj . I'm also excited to write up some demo's of y-py on client (pyodide) and server (fastapi). Are you going to bump the version, or want to manually push out the 0.5.4 emscripten wheel to pypi? |
closes #90.
I believe Pyodide needs a wheel built with a specific version of Python and specific version of emscripten that match the Pyodide version. For latest Pyodide (0.21.3, released Sep 15 2022), and going back through Pyodide 0.20.0 (Aug 9) that is Python 3.10.2 and emscripten 3.14.1. If we wanted to support earlier versions, we would need to review Pyodide changelog to make a matrix of python/emscripten versions to build the wasm wheel with.
See https://github.com/kafonek/ypy/actions/runs/3452230687/jobs/5761992236 for an example of the wheel being built. I don't understand why that's building a wasm wheel for py310 and py311 there but it doesn't hurt anything 🤷♂️ .