-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: build wheels #416
feat: build wheels #416
Conversation
FWIW, I've found it very useful to have a manual trigger for the cibuildwheel workflow, with optional input for the git ref to be built, and optional cibw build/skip override. That way, you can always use the latest build workflow to backfill wheels of old releases, e.g., for new Python versions. |
…into beckermr-patch-1
OK @esheldon shall we merge? |
I can attempt to push the wheels using the workflow dispatch once the PR is merged. |
How are you testing that the wheels work, are available through pypi etc? |
So available on pypi we cannot test. If the uploads fail when it tries, we'll see the failure in CI and so I am not worried about that. For testing the actual wheels, I am testing a single version of python (3.11 or 3.12 depending on the architecture). I use pytest directly running on the installed wheel. See the sections of the workflow that look like this:
|
Shall we merge here? |
This PR adds wheel builds.
to do: