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.

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

numpy 2.0 compatability #1185

Merged
merged 7 commits into from
Oct 23, 2024
Merged

numpy 2.0 compatability #1185

merged 7 commits into from
Oct 23, 2024

Conversation

ddkohler
Copy link
Contributor

@ddkohler ddkohler commented Jul 3, 2024

Making the transition to support the new API
https://numpy.org/doc/stable/numpy_2_0_migration_guide.html

Changes

Checklist

  • updated documentation (update "from" docs, example)
  • updated CHANGELOG.md
  • tests pass

ddkohler and others added 3 commits July 3, 2024 02:09
still need to deal with trapz --> trapezoid (not backward compatible)

be sure to change docs as well
@ddkohler
Copy link
Contributor Author

everything looks ready on our end; just waiting on an upstream fix (untzag/tidy_headers#20) to get this through

@ddkohler ddkohler marked this pull request as ready for review October 21, 2024 20:11
increment tidy_headers so there is no numpy 2.0 issue
@untzag
Copy link
Member

untzag commented Oct 22, 2024

Hi @ddkohler @rpm4, tidy_headers has finally been released to both PyPI and conda-forge

@untzag untzag closed this Oct 22, 2024
@untzag untzag reopened this Oct 22, 2024
@ddkohler ddkohler changed the title [WIP] numpy 2.0 compatability numpy 2.0 compatability Oct 23, 2024
setup.py Show resolved Hide resolved
@kameyer226 kameyer226 merged commit 56465df into master Oct 23, 2024
11 checks passed
@kameyer226 kameyer226 deleted the numpy-2.0 branch October 23, 2024 17:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

numpy 2.0
3 participants