pyodide / pyodide/pyodide-pack

Add test files unvendoring functionality

Open
#41 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
48
Forks
9
PR merge metrics
No merged PRs in 30d

Description

Recently, I provided pyodide-build's unvendor_tests() functionality as a separate unvendor_tests_from_wheel.py CLI script as a part of https://github.com/sympy/live/pull/26, to reduce the size of the SymPy wheel downloaded from PyPI.

Would it be a good idea for pyodide-pack to include such functionality as well, so that it can be used as a CLI tool for downstream projects like this?

As a further step, would it make sense to remove this functionality from pyodide-build, and make it call pyodide-pack as a part of the wheel build process in https://github.com/pyodide/pyodide-recipes?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing pyodide_build/buildpkg.py's unvendor_tests() with unvendor_tests_from_wheel.py and the related pyodide-pack CLI entry points. Review the linked pyodide-recipes wheel-build process and determine the intended ownership and interface. Done means the scope is agreed and the proposed downstream workflow is documented or implemented with appropriate tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.