Remove mention of obsolete default value for 'boundary' parameter.#12304
Merged
jacobtomlinson merged 1 commit intodask:mainfrom Mar 2, 2026
Merged
Remove mention of obsolete default value for 'boundary' parameter.#12304jacobtomlinson merged 1 commit intodask:mainfrom
jacobtomlinson merged 1 commit intodask:mainfrom
Conversation
Remove default value note for the 'boundary' parameter.
Contributor
Unit Test ResultsSee test report for an extended history of previous test failures. This is useful for diagnosing flaky tests. 21 files ±0 21 suites ±0 5h 4m 0s ⏱️ + 1m 2s Results for commit 647145d. ± Comparison against base commit 4195f5a. |
jacobtomlinson
approved these changes
Mar 2, 2026
Member
jacobtomlinson
left a comment
There was a problem hiding this comment.
Thank you for the docs update!
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.
Dear maintainers,
This is a minor update to the docstring of dask.array.overlap.map_overlap. From the function signature, the default value for
boundaryisNone(is it worth mentioning that'none'is equivalent toNone?).I looked at the Git Blame, and I guess the update of this parameter description fell in the cracks when #8397 and #8743 happened.
Best,
Marianne