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

Update exception in preparation of numpy 2.0.0 #6696

Closed

Conversation

dstrain115
Copy link
Collaborator

  • Per numpy 2.0.0 release docs:

"Warnings and exceptions present in numpy.exceptions (e.g, ComplexWarning, VisibleDeprecationWarning) are no longer exposed in the main namespace."

- Per numpy 2.0.0 release docs:

"Warnings and exceptions present in numpy.exceptions (e.g,
ComplexWarning, VisibleDeprecationWarning) are no longer exposed in the
main namespace."
@dstrain115 dstrain115 requested review from vtomole and a team as code owners August 1, 2024 16:23
@CirqBot CirqBot added the Size: XS <10 lines changed label Aug 1, 2024
@pavoljuhas
Copy link
Collaborator

pavoljuhas commented Aug 1, 2024

@dstrain115 - Should we perhaps merge #6693 instead?

That one was generated using the ruff tool per https://numpy.org/doc/stable/numpy_2_0_migration_guide.html.

Copy link

codecov bot commented Aug 1, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.82%. Comparing base (c25678e) to head (d610945).
Report is 3 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #6696   +/-   ##
=======================================
  Coverage   97.82%   97.82%           
=======================================
  Files        1074     1074           
  Lines       92126    92126           
=======================================
  Hits        90124    90124           
  Misses       2002     2002           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@dstrain115
Copy link
Collaborator Author

@dstrain115 - Should we perhaps merge #6693 instead?

Sounds good to me. I will close this one.

@dstrain115 dstrain115 closed this Aug 1, 2024
@pavoljuhas
Copy link
Collaborator

Sounds good to me. I will close this one.

Thanks. Can you PTAL at #6693?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Size: XS <10 lines changed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants