Viewing profile — hoodchatham

See also "Camus and Sartre: The Story of a Friendship and the Quarrel that Ended It" https://press.uchicago.edu/Misc/Chicago/027961.html

crates.io is for distributing source code, pypi is primarily for distributing wheels which contain a mixture of Python code and compiled shared libraries.

That video was a major inspiration for me and probably indirectly led to me becoming a Pyodide maintainer.

It says the same thing in the pyodide repl for what it's worth.

Reference types makes wasm/js interoperability way cleaner and easier. wasm-gc added a way to test a function pointer for whether it will trap or not. And JSPI is a standard since …

Yes, it has all the normal CORS restrictions. If you're curious, the PR that added support for this is here: https://github.com/urllib3/urllib3/pull/3195

The actual code example he made runs about 100 times faster in Spy/emscripten than in Pyodide.

Pyodide uses its own event loop which just subscribes to the JavaScript event loop. My suspicion is that this will be more efficient than using uvloop since v8's event loop is quit…

Are people maintaining wasi ports of Python 2.7 and 3.8?

I certainly think there's an 80/20 rule here. Most packages are not very hard to port, and generally the ones that are hard to build use features like threads and multiprocessing, …

As far as I'm aware, even discarding the instance isn't good enough, since v8 doesn't seem to reclaim the Wasm Linear Memory ever. I think the only thing you can do is start it in …

aiohttp is still work in progress but it works with a monkey patch. https://github.com/aio-libs/aiohttp/pull/7803

To be clear these are all use cases of Pyodide. PyScript only was released two days ago so it's harder to point to real world uses.

> Why? This isn't good for most web use cases but there are some major new use cases that it enables. Pyodide is in Python documentation all over the place, for instance on https:/…

Adding -Os to the Pyodide compilation flags has proven surprisingly hard: https://github.com/pyodide/pyodide/pull/1882 But some other low hanging fruit include unvendoring the spec…

Agreed, wasm loading is supposed to be cached but in practice it doesn't seem to happen.

I'm confused how this would work. What about METH_VARARGS | METH_KEYWORDS functions? These are declared with type PyObject* f(PyObject*, PyObject*, PyObject*), are cast to PyObject…