-
-
Notifications
You must be signed in to change notification settings - Fork 8k
TST: Fix runtime error checking NaN input to format_cursor_data #30162
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
Conversation
Looks like the Python 3.13 builds are hitting the broken installation python/cpython#135151 |
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.
Shouldn't the warning catch happen in format_cursor_data (or _format_cursor_data_override) so that it indeed doesn't get emitted when the user mouseovers a nan pixel?
Feel free to dismiss if I missed something.
Ah, I wasn't sure if that was something that would happen on purpose; if so, then yes we can move it there. |
@timhoffm Still OK with the new version? |
…ut to format_cursor_data
…162-on-v3.10.x Backport PR #30162 on branch v3.10.x (TST: Fix runtime error checking NaN input to format_cursor_data)
PR summary
This seems to have changed in NumPy 2.3.0, only on Windows, but there's no reason to not catch this in the test always.
PR checklist