Gyeongjae Choi

I think we can wait for the upstream PR https://github.com/aio-libs/aiohttp/pull/7803, since aiohttp won't work until the patch is accepted to upstream.

It looks like `numpy` is a build dependency of `pandas` but it is not declared in the `pyproject.toml` of Pandas 2.0.0. I guess this is fixed in Pandas 2.1.0 so...

Yes, it seems like onnxruntime has [some build dependencies](https://github.com/microsoft/onnxruntime/blob/8d503138168d4ae54869c82b1032a38c6cb9f3a7/tools/ci_build/build.py#L817-L823) but they are installed inside complex build script, instead of [using standard way](https://peps.python.org/pep-0518/). One possible way of handling it in Pyodide...

Hi, @ddl-aj-rossman! All the packages you added in this PR seem like a pure Python wheel that is [installable with the micropip](https://pyodide.org/en/stable/development/new-packages.html#determining-if-creating-a-pyodide-package-is-necessary). So I think you don't need to add...

> We're trying to cut down on the time required to get up and running with the notebook. I see. You don't need to build the Pyodide from scratch for...

Thanks for the contribution @gorondan. `web3.py` seems to have quite a few dependencies, most of which can be installed with micropip since it is a pure python package. Therefore, not...

This looks like a file system issue. As far as I know, the jupyterlite team implements and uses its own file system, so you might need to open an issue...

> Yes, ideally that should fail. @ryanking13 I wonder if we can copy-paste slightly better file name checking logic from packaging, or vendor the file that implements that, or something....

Thanks for the info and for your contribution to deno support @rajsite!

Thanks! I just transfered the repository to https://github.com/pyodide/pr-integrator. Please let me know if there is any issue.