Repository navigation
Suppress NumPy 2.4 VisibleDeprecationWarning for align=0 in test - #822
Merged
Merged
Conversation
… compatibility tests
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #822 +/- ##
==========================================
+ Coverage 2.14% 99.33% +97.18%
==========================================
Files 26 26
Lines 884 898 +14
==========================================
+ Hits 19 892 +873
+ Misses 865 6 -859 🚀 New features to boost your workflow:
|
d-v-b
approved these changes
Mar 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Old
.npyfixture files and pickled data contain NumPy dtype descriptors withalign=0(an integer). NumPy 2.4 deprecated this, requiringalignto be a boolean, which causesVisibleDeprecationWarningto be raised duringnp.load(),pickle.loads(), and.view(dtype=...)calls.I added
warnings.catch_warnings()filters incheck_backwards_compatibility()to suppress this warning in the three affected code paths (fixture loading, codec decoding, and dtype view).The fixture data itself remains untouched — the backwards compatibility tests continue to validate that old encoded data can still be decoded correctly.
Claude assisted in these changes
Closes #821
TODO: