-
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
Bump CIBuildWheel Version to 2.15.0 #70
Conversation
Thanks for the PR! Can you bump |
Done! I went with the most minor version increment but let me know if you'd like something else. |
Thanks for the fixes!! Sorry I'd fix these locally but I don't have the project open. I think to fix the build we need to:
|
No problem at all, thank you for your help! I cloned the repo and made the changes you requested, and it looks like the wheels build with |
Hmm, looks like black is still failing, I'll see about fixing that. |
Looks close! It seems like everything except 3.12 is working, which appears to be surfacing a bug/deprecation in setuptools? Looks like it's this one: pypa/setuptools#3935 |
Ah yep, distutils is deprecated in 3.12 according to https://peps.python.org/pep-0632/. Unfortunately I'm not really sure how to fix this one. |
Yeah 🥲. I think we're blocked until numpy/numpy#23808 gets fixed? |
Oh actually this looks like it could plausibly work:
|
Seems to work in 3.12 now! Hopefully the actions pass. I made a slightly different version that kept |
Looks like it's building now, only failing on 3.12 tests 😆. Thanks for all the followup on this PR! It's a little suspicious python-fcl currently only has numpy in the build-system (which I don't know if the install respects?) I suspect it might need the version-locked numpy in
|
Ah good point. With this change I can now install properly in 3.12, so hopefully it'll fix the problem. |
Shoot now it looks like there's a mismatch.... |
Oh I wonder if this version range needs something for Python 3.6, or to drop Python 3.6. FWIW I've had to drop 3.6 on other projects due to
|
Hmm I would think it would just work, since for older versions like 3.6 it should fall back to |
Oh looking at the logs my theory on this is that we're double-specifying the build system in both
|
Hmm, so does that mean we would want something like this?
Since if we take the numpy specification out of both blocks in |
Looks like you got it great work! Thanks for the follow ups, these CI changes are particularly rough haha. I think at some point this project should probably use |
Great! Thanks for guiding me through the process and for maintaining the project! |
To address Issue #69