Simon Biggs <simon.grant.bi...@gmail.com> added the comment:
Hi pmp-p and Serhiy, I'd be more than happy to attempt a pull request, but I imagine a change such as this needs to be discussed first, trying not to "rush to make a patch" (https://www.youtube.com/watch?v=voXVTjwnn-U&feature=youtu.be&t=2546). Also, I doubt I will do a good job of it... but I am more than happy to try. A note regarding "supercharged full stack pyodide", potentially without efforts such as upstreaming into CPython and emscripten the relevant patches, that supercharged full stack may just unfortunately stagnate. See https://github.com/iodide-project/pyodide/issues/635#issuecomment-613408912 With respect to blocking when running Python as WASM, I have found running the WebAssembly CPython within a webworker and signalling data back and forth causes there to be no UI issues. It ends up being quite a neat set up. Main down side right now however is the set up is currently going stale, hence me believing reaching out like this is in the best interests of Python going forward. Cheers, Simon On Tue, 14 Apr 2020 at 18:58, pmp-p <rep...@bugs.python.org> wrote: > > pmp-p <pmpp....@gmail.com> added the comment: > > you can add > * > https://github.com/pmp-p/pydk/tree/master/sources.em/Python-3.8.0b4.patchset > -- Python 3.8.x > > (wasm not asm.js, clang-10+ required) > > demo https://pmp-p.github.io/python-next/test.html > > CPython can already run in the browser with very little patching, but > major issues are : > > - asyncify'ing the whole wasm VM to have pre-emption over cPython's one > to prevent blocking I/O slows down things *a lot* (10x) > => (very?) bad user experience. > > - the size of vm + stdlib ~ 30 MiB and wasm compilation time. > => bad user experience on first load or slow connexion. > > - the lack of threading in wasm MinimumViableProduct specification (but > this is the browser standard for now), that leads to rewrite bits of stdlib > ( like eg asyncio module ) > => adding more maintenance burden on stdlib (!) > > > i tested them all and my personnal opinion is : I can see no use case that > would favour "stock" cPython wasm versus a blazing fast MicroPytho (or > pycopy) wasm flavour or supercharged full stack pyodide. > > ---------- > nosy: +pmpp > > _______________________________________ > Python tracker <rep...@bugs.python.org> > <https://bugs.python.org/issue40280> > _______________________________________ > ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue40280> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
