Compare test data's content generally #379
Closed
Conversation
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
7 tasks
|
Thoughts @zarr-developers/core-devs? |
Instead of strictly expecting values returned from a store to be `bytes` instances only in the tests, relax this to anything that supports the buffer protocol and has the expected content. This makes it possible to return things like NumPy `memmap` objects and still have the tests work correctly.
|
Consolidating back into PR ( #377 ). |
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.
Instead of strictly expecting values returned from a store to be
bytesinstances only in the tests, relax this to anything that supports the buffer protocol and has the expected content. This makes it possible to return things like NumPymemmapobjects and still have the tests work correctly.TODO:
tox -e docs)