DEP: Remove numerical arguments from convolve2d / correlate2d #8542
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.
As mentioned in #8413 (comment), it has never actually been possible to set the boundary using an integer, since
_bvalfromboundaryhas been broken since it was created 17 years ago, raisingUnboundLocalError: local variable 'val' referenced before assignment.The mode argument
_valfrommodewas initially broken the same way, but fixed shortly afterward .But if no one noticed that it doesn't work for
boundary=in the last 17 years, it seems like numeric parameters are not commonly used. Also they are untested, and were removed from the documentation 8 years ago.Is there any benefit to supporting them?