I spent some time today getting acquainted with python-wasm...

[williamstein]

This is from @DrXyzzy , but I'm copying it here so it's public.

#wasm I spent some time today getting acquainted with python-wasm. I did all my tests in a CoCalc project. As non-root, I upgraded node in the project to node-v18.6.0. Then I installed the package with npm install python-wasm and also did a git repo clone and built from source. By looking at the source repo, I was able to run the webpack and terminal modules. So far, i'm just confirming existing docs.

Things I would like to do for further testing. I have no idea how hard/feasible any of these are:

1. Do a pip install of a package with dependencies. Most Python programming I do these days uses pandas, which has a lot of dependencies.
2. Read and write files from/to my computer or a Cocalc project, somehow, for example mounting a folder to the wasm filesystem.
3. Copy in a cocalc shared folder, including ipynb and/or sagews and data, and run the code.

[williamstein]

#wasm

As non-root, I upgraded node in the project to node-v18.6.0.

Cool, since I haven't even tried node 18.x yet! I've only tried 16.x.

I just pushed out a major update a few minutes ago. The big new feature is that if you do

for i in range(10**8): print(i)

then hit control+c, it actually interrupts! Try that with pyodided or jupyterlite, and you get stuck forever. You can try this immediately at https://python-wasm.cocalc.com/ which is running the latest version.

Do a pip install of a package with dependencies. Most Python programming I do these days uses pandas, which has a lot of dependencies.

This will not work at all, even in the slightest. First, pandas uses lots of Cython, and there is zero support for extension modules. I haven't even started to implement dlopen. Keep your eye on #9. I just have to reimplement dlopen and friends... somehow porting that 1000-line javascript code linked to in the above issue to zig + typescript. I'm planning to start that next.

Read and write files from/to my computer or a Cocalc project, somehow, for example mounting a folder to the wasm filesystem.

If you use python-wasm via the nodejs terminal, then that will already just work. It has full read/write access to exactly your existing filesystem with no config needed. If you want to do that in the browser, that's #4. You can read/write the ramdisk already, but there is no way to upload or download anything to/from it.

Copy in a cocalc shared folder, including ipynb and/or sagews and data, and run the code.

I'm not sure what this means...