Emscripten build with NODERAWFS=1 #36
Comments
|
Yeah more broadly we should try building with Emscripten targeting node as that will be easier to test |
emmatyping
added a commit
to emmatyping/cpython
that referenced
this issue
Jan 9, 2022
This adds a "python.js" target to the Makefile. We enable the raw node fs mode as suggested by @thomasballinger as it will make running the test suite under node easier, c.f. emmatyping/python-wasm#36. The wasm_asset.py script is updated to include the test module. Care is taken to skip compiling the Python files that are examples of bad syntax or encoding. This also turns on memory growth as early into the test suite I was running into OOMs.
|
Fixed in python/cpython#30552 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It might be helpful for tests? being in a more familiar environment? to do an emscripten build that uses the native filesystem, which is possible with NODERAWFS replacing the Emscripten in-memory filesystem. This would get us close to something like
node python.js script.py.FIle permissions don't quite work the sameThere are some limitations to going through this layer, but it's pretty seamless for the filesystem access that node does provide. This might let folks install the emscripten-compiled version of Python alongside other python builds like pypy.WASI support seems strategically more important, but this could be a useful foothold.
The text was updated successfully, but these errors were encountered: