-
-
Notifications
You must be signed in to change notification settings - Fork 346
improvements to parse_dtype
#3264
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
Merged
Merged
Changes from all commits
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
ed56505
add parse_dtype as ergonomic replacement for parse_data_type, handle …
d-v-b ca6196d
Merge branch 'main' of https://github.com/zarr-developers/zarr-python…
d-v-b d04557d
update docs
d-v-b 6009923
changelog
d-v-b 082ad49
remove type: ignore
d-v-b b54bbe3
Merge branch 'main' into widen-parse-data-type
d-v-b d684ada
add test to check that parse_dtype is parse_data_type
d-v-b 5feb937
Update src/zarr/dtype.py
d-v-b c42edf6
fix docstring
d-v-b d234ae2
Merge branch 'main' into widen-parse-data-type
d-v-b 6285005
support the output of to_json(zarr_format=2) as input to parse_dtype
d-v-b 3a82a26
Merge branch 'widen-parse-data-type' of github.com:d-v-b/zarr-python …
d-v-b b95f3be
lint
d-v-b b0edab6
remove infinite recursion
d-v-b 385efa0
Update src/zarr/core/dtype/__init__.py
d-v-b f7b5387
Update src/zarr/core/dtype/__init__.py
d-v-b 6cef7d7
Update src/zarr/core/dtype/__init__.py
d-v-b 9a7d1db
Update src/zarr/core/dtype/__init__.py
d-v-b d741513
Update src/zarr/core/dtype/__init__.py
d-v-b 8585158
Update src/zarr/core/dtype/__init__.py
d-v-b 8d2c0f0
Merge branch 'main' into widen-parse-data-type
d-v-b File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
- Expand the range of types accepted by ``parse_data_type`` to include strings and Sequences. | ||
- Move the functionality of ``parse_data_type`` to a new function called ``parse_dtype``. This change | ||
ensures that nomenclature is consistent across the codebase. ``parse_data_type`` remains, so this | ||
change is not breaking. |
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
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
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
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
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
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
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
Oops, something went wrong.
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.
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.
A stretch goal (for another issue/PR) - would it be possible to make this optional for certain inputs (e.g., converting 'int32' doesn't depend on the version of the zarr spec)
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.
I would rather not have a function where one parameter is optional depending on the value of another parameter. That should probably be a different function entirely, e.g. one that specifically takes numpy dtype-like inputs and finds the corresponding zarr data type.