Pyodide 0.28 blog post #53
Conversation
❌ Deploy Preview for pyodide-blog failed.
|
|
Thanks @agriyakhetarpal this is really helpful. |
|
Since we put so much effort into the release notes and work on them at the last minute they often end up delaying the release so frontloading any of that work is great. |
Co-Authored-By: Hood Chatham <[email protected]>
|
Thanks Hood, I linked PEP 783 as well. Let's hope to revisit this closer to the release and add more items. |
✅ Deploy Preview for pyodide-blog ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Thanks for writing the draft @agriyakhetarpal! I have added things I want to include in the release note. Please feel free to modify if there is something you want to highlight more, or if there are any awkward sentences. |
|
I'm going to push a few changes here! Thanks! |
|
I committed some of my own suggestions, please feel free to modify the branch directly of course! |
agriyakhetarpal
left a comment
agriyakhetarpal
left a comment
There was a problem hiding this comment.
Ensuring consistency for the headings (Sentence case instead of Words Start With Capitals)
ryanking13
left a comment
ryanking13
left a comment
There was a problem hiding this comment.
Thanks for polishing up the changelog! It looks good me.
| able to upstream fixes to the Emscripten dynamic loader. It also forced us to | ||
| load dynamic libraries eagerly rather than lazily. | ||
|
|
||
| We added runtime path to the WebAssembly specification for the shared library |
There was a problem hiding this comment.
| We added runtime path to the WebAssembly specification for the shared library | |
| We added runtime path to the Emscripten specification for the shared library |
To be precise, I think it is Emscripten not WebAssembly. There is no spec for dynamic loading in WASM spec.
There was a problem hiding this comment.
Well it lives here:
https://github.com/WebAssembly/tool-conventions
So I think it's a WebAssembly spec.
There was a problem hiding this comment.
These conventions are not part of the WebAssembly standard, and are not required of WebAssembly-consuming implementations to execute WebAssembly code. Tools producing and working with WebAssembly in other ways also need not follow any of these conventions. They exist only to support tools that wish to interoperate with other tools at a higher abstraction level than just WebAssembly itself.
Yeah, but it is a convention, not a standard. Of course, LLVM supports it, and Google would want to standardize it. Anyway, I just wanted to mention it—no changes required.
I'm pre-emptively adding draft release notes with points for the upcoming Pyodide 0.28 release, which we can fill out when we are closer to the release milestone. Please feel free to push directly to this PR and add/modify content as needed.