Skip to content

Build per-platform wheels and run the corpus against them - #2

Draft
suleman-uzair wants to merge 4 commits into
feat/python-ctypes-runtimefrom
feat/python-native-wheels
Draft

suleman-uzair wants to merge 4 commits into
feat/python-ctypes-runtimefrom
feat/python-native-wheels

Conversation

@suleman-uzair

Copy link
Copy Markdown
Collaborator

Builds per-platform wheels that carry the pinned core's C library and runs the conformance corpus against each installed wheel. Refs ukiryu/ukiryu#25 (part of ukiryu/ukiryu#29). Stacked on #1; the base is that branch.

Changes

  • pyproject.toml, setup.py: platform wheels tagged py3-none-<platform>, with the library at ukiryu/lib/. The tag comes from UKIRYU_WHEEL_PLAT, never from the build host. No sdist.
  • .github/workflows/wheels.yml:
    • Build: Linux x86_64 and aarch64 inside manylinux_2_28 images, macOS arm64 (11.0) and x86_64 (10.15), Windows x86_64 with a static CRT.
    • Install: each wheel goes into a clean venv on Python 3.9 and 3.13, run from a copy of tests/ outside the checkout with python -I. It runs the installed-wheel checks, the binding tests and the full corpus. Linux also runs the corpus in a manylinux_2_28 image (glibc 2.28).
  • scripts/check_wheel.py: checks the library's own baseline (max GLIBC symbol, Mach-O minos, no VC++ runtime import on Windows) and records wheel, library and core hashes plus the core commit.
  • tests/wheel/: the loaded package is the installed one, the library source is packaged, and its hash equals the build record.

Not done here

  • Publishing. The wheels are workflow artifacts only. The package name, version and Python floor in pyproject.toml reuse what the repo already has and are not a ratified release contract.
  • The core pin is still the ukiryu-rs#66 head, so the corpus result depends on it. Add the ctypes Python binding over the core C ABI #1's CI shows 3 of 13924 rows differing on YAML syntax-error message text.

suleman-uzair added 4 commits November 16, 2026 20:37
Add a wheel build for Linux (manylinux_2_28 x86_64 and aarch64), macOS
(arm64, x86_64) and Windows x86_64 that bundles the pinned core library,
checks its glibc, macOS or Windows baseline from the binary, and records
wheel, library and core hashes. Each wheel is installed into a clean
environment and runs the binding tests and the conformance corpus. Wheels
are workflow artifacts only; nothing is published.
A distribution without extension modules put the package under
.data/purelib. Declare platform content so the wheel root holds it.
A queued macOS runner held every platform's install test back because the
install job needed the whole build matrix. Install and test each wheel in
the job that built it, and keep running later checks after an earlier one
fails so one result does not hide another.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant