Skip to content
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.

Sign up for GitHub

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

Jump to bottom

complete numpy 2.0 migration #249

Closed
mmckerns opened this issue Aug 1, 2024 · 0 comments · Fixed by #252
Closed

complete numpy 2.0 migration #249

mmckerns opened this issue Aug 1, 2024 · 0 comments · Fixed by #252
Labels
compatibility

Comments

@mmckerns
Copy link
Member

mmckerns commented Aug 1, 2024

Complete migration of code for changes in numpy 2.0
https://numpy.org/devdocs/numpy_2_0_migration_guide.html

Specifically, things like testing for int may need to be expanded to `np.int64' , and anything not caught in #248
@shinnar shinnar mentioned this issue Aug 6, 2024
Merged
shinnar added a commit to IBM/lale that referenced this issue Aug 6, 2024
@shinnar
docs: Remove numpy upper bound from docs build and mock mystic (#1381)
4b7e7ce 
the latest release of mystic does not yet support numpy>=2.0.
At least one of the issues has been fixed in master: uqfoundation/mystic#248
and there is an issue for completing the migration: uqfoundation/mystic#249

This addresses #1375

Signed-off-by: Avi Shinnar <[email protected]>
@mmckerns mmckerns mentioned this issue Sep 9, 2024
Merged
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
compatibility
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

type check with Integral, bool by value uqfoundation/mystic
1 participant
@mmckerns