Gyeongjae Choi

We appreciate the report, but it's difficult for us to resolve this issue without information on the situation in which it is happening.

The list in `https://pyodide.org/en/0.22.0a3/usage/packages-in-pyodide.html` is incorrect. The `gdal` package in that list means the shared library (libgdal) not the `gdal` python package. We removed the non-python packages from that list,...

@vigouredelaruse Sure, please open a PR to rename gdal to libgdal in the recipe. I think we can accept that.

I also think this is working as intended. > It seems like capturing error output accurately would be a important feature of a project like this, but at the moment...

Conceptually and physically, Pyodide is more of a library than a process. It's not a process, so it doesn't terminate on error, and it doesn't have an exit code. If...

> As for as updating documentation, what is the procedure for that? Are the docs a part of this repo, or hosted elsewhere? You can read the documentation about [Error...

@jsilter not very much, but we can help you debug the build if you open an issue.

My thoughts are still the same as the comment above (https://github.com/pyodide/pyodide/issues/3938#issuecomment-1598546005), I think it's more natural to throw an exception than to print an error to stderr. However, if a...

> in my example nobody can catch that error outside pyodide internals though ... we can't wrap every branching async code or listener, we have only stderr to hook into...

Cool! I guess we need to try building pyarrow (#2933) after this PR, since many people will want to use pyarrow in pandas 2.0 :)