-
Notifications
You must be signed in to change notification settings - Fork 451
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
release before numpy=2.0
?
#1974
Comments
In case anyone is having weird pint errors, or getting this error: AttributeError: module 'numpy' has no attribute 'cumproduct'. Did you mean: 'cumprod'? It's because you installed Numpy 2.0.RC1, which isn't yet supported. |
I'm not sure how best to handle the |
I would forward #1960 is a documentation-only PR (and from a quick glance I can't see anything wrong), so I think that PR is fine? |
We're officially on the clock here, as NumPy 2.0 will release 16 June 2024. It would be good to get some kind of release out the door since currently importing pint with numpy 2 installed results in the I'm going to update on conda-forge to add a constraint for numpy < 2. |
Do we know what issues still remain here? Curious if anyone has tried to run the test suite with NumPy 2. If so, would be curious to know what that reveals |
I've released a pre-release. We've said to leave a week before full release so 0.24 can be released on the 8th. |
numpy>=2
will include a couple of breaking changes (to be released soonish), so it would be good to have a release ofpint
before that (I'd also love to have #1922 in a release, as it will fix some typing issues onpython>=3.12
)Most of the urgent issues have already been fixed, the only thing left is #1971.
Other than that,
__array__
has gained a optionalcopy
kwarg which we should add (the version of__array__
withoutcopy
will cause a deprecation warning).The text was updated successfully, but these errors were encountered: