Juniper Tyree

Thanks for the ping but I'm afraid I can't help much myself. I can merge PRs in this repo, but I've never worked on the IntelliJ plugin myself and have...

> What is the performance impact of converting all source errors into rust compared to a plain PyErr? At the moment, this conversion scales linearly with the length of the...

You can also first import the `pyodide-http` package, which patches requests and urllib to work inside WASM: ```python import pyodide_http pyodide_http.patch_all() # now the rest ... ```

Sort of ... it's the semi-recommended way at the moment (see https://pyodide.org/en/stable/project/related-projects.html#workarounds-for-common-wasm-and-browser-limitations). In my own projects where I self-host Pyodide, I try to hide this detail by always installing the...

If you use urllib3 (which your first patch seems to do), everything might even work without any need for pyodide-http since urllib3 now contains upstream Emscripten support.

If you prefer the pyodide-http patch, could you just check the import and apply the patch at the top level so it's only a very short diff?

+1

> In the future, JSPI will help this situation, as after JSPI we will no longer have to pre-load all the shared libraries in the package, but load them on...

I've been experimenting a bit with what synchronous package loading will look like (not using JSPI but by hacking together a `loadPackageSync` function, see https://github.com/climet-eu/pyodide/compare/climet-lab-0.27.0...climet-eu:pyodide:climate-lab-0.27.0-syncify, everything built on top should...

If you have ideas for how to hack around with lazy dynamic library loading, (e.g. would only pre-loading the indirect dependencies in the ".libs" folder work to hack around the...