Gyeongjae Choi
Gyeongjae Choi
### Description This removes `[deploy]` dependencies from pyodide-build, and puts them under the `requirements-deploy.txt` in the root directory. If these packages are defined in pyodide-build, they create a dependency that...
## Proposed refactoring or deprecation We are "unvendoring" some libraries to reduce the size of the Pyodide main module, and these libraries are being built as recipes like any other...
### Description A tiny PR that allows passing env variables when building recipes. For example, `EMCC_DEBUG=1 pyodide build-recipes ...` didn't work before this PR, as EMCC_DEBUG=1 was not passed to...
### Description The goal of this PR is to reduce the dependency on pyodide for testing pyodide-build. The main changes are: 1. Add a new fixture: `mock_emscripten` for mocking emscripten...
## Proposal Overview This issue proposes to decouple the versioning of the pyodide-build and the Pyodide distribution, so that we can release new versions of the pyodide-build without having to...
This PR adds [PEP 658: Serve Distribution Metadata in the Simple Repository API](https://peps.python.org/pep-0658/) support to micropip, which means that when using Simple API to install a package, micropip will check...
`micropip.freeze` is now used in `pyodide-pack` (https://github.com/pyodide/pyodide-pack/pull/31), but I think [we don't have strong enough test cases for micropip.freeze](https://github.com/pyodide/micropip/blob/main/tests/test_freeze.py). So I think it would be good to add some tests...
We parse and compare versions lots of times when searching for an appropriate package, but parsing and comparing Version (`packaging.version.Version`) is quite expensive. See: https://github.com/pyodide/micropip/pull/71#issuecomment-1630859157 So it would be nice...
Resolve #51 ~~This PR changes `micropip.install` behavior to remove previously installed packages and reinstall the new version. In addition, it adds the `force_reinstall` parameter to `micropip.install`, allowing it to force...