While working on pyodide/pyodide-build-environment-nightly#79, I had a chance to read through the contents of our 55 nightly xbuildenv releases, and found that we used to include numpy, scipy, numpy-tests, and scipy-tests. Later on, we stopped including numpy-tests, especially after splitting NumPy into numpy and numpy-tests recipes. Setting a reminder here that we should do it for SciPy as well, and create a standalone packages/scipy-tests/meta.yaml recipe with only min-scipy-stack tag and no cross-build tag.
That said, someday, if we add more such packages (not really needed now), when writing the xbuildenv's pyodide-lock.json, we should filter out entries where "unvendored_tests": true is set in our create_xbuildenv.py in Pyodide.
My rationale is that the xbuildenv size has been increasing from 5 MB to 7 MB. It is not a large increase by any means, but there is no need to include unnecessary packages that are not used in a cross-build environment.
While working on pyodide/pyodide-build-environment-nightly#79, I had a chance to read through the contents of our 55 nightly xbuildenv releases, and found that we used to include
numpy,scipy,numpy-tests, andscipy-tests. Later on, we stopped includingnumpy-tests, especially after splitting NumPy intonumpyandnumpy-testsrecipes. Setting a reminder here that we should do it for SciPy as well, and create a standalonepackages/scipy-tests/meta.yamlrecipe with only min-scipy-stack tag and no cross-build tag.That said, someday, if we add more such packages (not really needed now), when writing the xbuildenv's
pyodide-lock.json, we should filter out entries where"unvendored_tests": trueis set in ourcreate_xbuildenv.pyin Pyodide.My rationale is that the xbuildenv size has been increasing from 5 MB to 7 MB. It is not a large increase by any means, but there is no need to include unnecessary packages that are not used in a cross-build environment.