openzim / openzim/python-libzim
Build for ABI3
- Dominant language
- Python
- Stars
- 108
- Forks
- 29
- Avg merge
- 9d 1h
- Merged PRs (30d)
- 1
Description
At the moment we build each release for all supported Python version at time of release.
Instead, we could build for the Stable ABI and have one wheel per platform instead of one per platform per python runtime and version.
The main benefit is that when a new Python version is available (beta, rc, released), one can use our existing wheel.
Another benefit is that release build time should be greatly reduced (currently more than 2 hours).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the release build configuration and the Python extension entry point, then compare the current per-runtime wheel matrix with the Stable ABI requirements linked in the issue. Done means producing one compatible wheel per platform, usable across supported Python versions, while confirming the release build no longer requires every runtime-specific build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100