-
Notifications
You must be signed in to change notification settings - Fork 159
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
Compatibility with numpy 1.24 #325
Conversation
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.
Having the same problem. If I understand correctly, just using int
instead of np.int
should solve the problem. Is there any advantage for np.int_
?
According to the numpy documentation, |
Thanks! This is how I'm reading numpy's message. 😀 |
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.
Thanks for finding time!
Let's hope someone merges it. 🤞🏻 Need someone with write access to the repo, right?
@dswah Could you approve? |
Looks like the necessary changes were made to the main code and a new version released recently. I will close the PR. Thank you for getting the new version out. |
With the latest release of numpy 1.24.0, numpy deprecated and removed
np.int
. This PR replacesnp.int
withnp.int_
. The change was tested using numpy 1.23.5 and numpy 1.24.1 with Python 3.10.9.If you merge the PR, please release a new version of pyGAM on pypi.
Closes #326