Fix dblquad and tplquad not accepting float boundaries #8661
Conversation
This file contains 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
|
Makes sense. Thanks @vkk800 |
StrahinjaLukic
pushed a commit
to StrahinjaLukic/scipy
that referenced
this pull request
Apr 14, 2018
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.
This is a simple fix to make dblquad() and tplquad() functions accept numbers (instead of just functions) as boundaries for the integration. I'm not sure if the previous behaviour was a bug or done like that on purpose, but since nquad() (which dblquad and tplquad use) accepts numbers as boundaries, it seemed inconsistent to me.
I also changed the documentation and added a simple unit test to reflect this change.