-
Notifications
You must be signed in to change notification settings - Fork 119
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
[WIP] Backport 8.2: Python 3.13 support #3319
base: release/8.2
Are you sure you want to change the base?
Conversation
0c2b646
to
4636714
Compare
39) numpy_ver="numpy>=2" ;; | ||
310) numpy_ver="numpy>=2" ;; | ||
311) numpy_ver="numpy>=2" ;; | ||
312) numpy_ver="numpy>=2" ;; | ||
313) numpy_ver="numpy>=2" ;; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is because numpy 2 is backwards compatible, but numpy 1 is not forwards compatible, so building a wheel with numpy 1.x and testing it with 2.x will fail, but the other way around works.
It looks like you're in some sense resurrecting my failed attempt (subsequently reverted) in #3317 to adopt master methods for ci into release/8.2. I'm speculating that my further attempts to manually and minimally just increase the list of pythons in release/8.2 is making good progress even though ci currently rests at 33 failing and 6 successful checks. |
Init submodules before running cmake
edeacd4
to
6e9d626
Compare
Quality Gate passedIssues Measures |
✔️ 8ad39c1 -> Azure artifacts URL |
Uses #3317 as baseline. Also backported #3028, #3040, and part of #1969.