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
Add support for CIBW_ENVIRONMENT #149
Comments
I think this should already be possible with the |
Indeed, |
So while this works, it also un-discriminatorily pulls down numpy 1.26b for everything, not just the cp312 stuff. This also breaks all the env: |
CIBW_ENVIRONMENT: PIP_PRE=1 What is the best way to tell the workflow to only do it for certain Python version here? Or do I need a totally separate workflow just for cp312. |
You could try: env: |
CIBW_ENVIRONMENT: 'PIP_PRE=$( if [ "${CIBW_BUILD:0:5}" = "cp312" ]; then echo 1; else echo 0; fi )' A neater solution might be to configure |
Alas, something isn't quite right in the if-else syntax you provided. The "else" seems to work but "then" failed to assign 1 to the variable. I get this:
|
I need something like this to build wheel for Python 3.12 for packages with C stuff that needs unreleased numpy 1.26b. Unfortunately, I don't know if it is possible from your workflow here. Please help. Thanks!
https://github.com/scipy/scipy/blob/34366e000b3f37732c4254476e0d6df1857f1f70/.github/workflows/wheels.yml#L136C11-L136C27
Related PRs:
The text was updated successfully, but these errors were encountered: