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

Nick/numpy 2 #307

Merged
merged 9 commits into from
Oct 23, 2024
Merged

Nick/numpy 2 #307

merged 9 commits into from
Oct 23, 2024

Conversation

ntjohnson1
Copy link
Collaborator

@ntjohnson1 ntjohnson1 commented Jun 30, 2024

Resolves #306, #309

All of this is mostly superficial, I expect we'll be tracking down the fact that a numpy scalar now prints a np.float32_(2.0) instead of 2.0 for a while. But this captured everything unhappy in all of our tests. I ran python3.8 and python3.9 (with numpy 2.0) against all our tests so I'm reasonably confident this will clear CI, but my permissions changed so I'm no longer able to trigger it myself when I submit a PR hmm I guess CI does run for me but I am not able to trigger it on other MRs.

I tagged on the typing_extension bit since that also is a broken pyproject config on main at the moment.


📚 Documentation preview 📚: https://pyttb--307.org.readthedocs.build/en/307/

* Convert numpy scalars to python with .item
* Make sure inputs to numpy groupies first arg is a row vector
* Replace in1d
* Convert numpy scalars to python with .item
* Fix some minor typing changes
@ntjohnson1 ntjohnson1 requested a review from dmdunla June 30, 2024 18:00
@dmdunla dmdunla merged commit 3da840e into sandialabs:main Oct 23, 2024
9 checks passed
@ntjohnson1 ntjohnson1 deleted the nick/numpy_2 branch October 24, 2024 06:36
@ntjohnson1 ntjohnson1 mentioned this pull request Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support Numpy 2.0
2 participants