Document the behavior of converting a Dask array to a Python number #10686
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.
Document the behavior when converting Dask arrays to Python numbers (bool/int/float/complex): https://dask--10686.org.readthedocs.build/en/10686/array-api.html#array
I noticed that there was some discussion on whether or not this is a desirable feature in #9387, but I thought it would be useful to document it anyway as this will help to avoid confusion.
For us, this feature is quite useful because it allows us to write e.g.
and that will work regardless of whether
a
is a numpy or a Dask array.pre-commit run --all-files