Simon Willison highlights the Pyodide/WebAssembly architecture and its limits
3 Sep 21 6:25 PM · 2d ago · 1 article · 1 source · development 3 of 3
Developer Simon Willison wrote up how Python Workers run Python compiled to WebAssembly via Pyodide inside Cloudflare's V8-based workerd runtime, noting this brings some limitations including around multiprocessing.
“This comes with some limitations, documented here - most notably both multiprocessing…”
Simon WillisonCloudflare Platform vendorGyeongjae Choi Cloudflare engineer, blog co-authorDominik Picheta Cloudflare engineer, blog co-authorHood Chatham Cloudflare engineer, blog co-authorSimon Willison Independent developer/commentator
The whole story articlesposts the bright band is this development · numbered dots are the others · click one to jump
What was reported 1 claim about this development
-
first by Simon Willison, 2d ago
What people said 6 voices · verbatim
-
Great work from the Cloudflare team!I was very excited when they first launched Python Workers two years ago. Even though we have competing products at Wasmer, I think Cloudflare work is always exciting and inspiring.I went back to the feedback I posted in the original launch thread [1]. It's great to see that they have made meaningful progress…
-
> we contributed upstream to ensure these HTTP clients can route requests directly through the JavaScript `fetch` API in WebAssembly environmentsSome context from an urllib3 maintainer:urllib3 received and merged large contributions adding Pyodide/Emscripten support a few years ago, and later JSPI support, which is what made this work for…
-
I think this showcases the other issue I commented a few years ago [1].Pyodide and Cloudflare don't use the real network stack for http requests (they patched the functions to use JS `fetch` underneath). They also patched Python's async event loop to use JS event loop.This has a major downside: incompatibility issues. JS event loop is preemptive…
-
> I'm glad the work was contributed upstream and is useful to Pyodide and Cloudflare. But I think there is a meaningful difference between funding a contribution to an upstream project and funding the upstream maintainers who have to support it afterwards.Any of the upstream maintainers consider blocking merge unless Cloudflare signs a support…
-
Have we come back full circle back to GAE [1], launched in 2008 with Python 2.5 support ...[1]
-
It always seemed so strange to me that "native" http clients were so lousy or many cases even non-existent considering that that's half of development these days.
All 3 developments of Cloudflare takes Python Workers out of preview into general… →
NewswiresHacker NewsMastodon