fix airy function deprecations (follow-up to #18050) #19776
Closed
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.
I noticed that the recent
airy
deprecation warnings added in #18050 were throwing errors due to the (un)layered quoting, so I fixed it. Should I add tests for this, or do we not do tests for depwarns?This reveals another bug which I'd also be happy to fix, if somebody wants to tell me what to do (I'm not very familiar with these functions, other than needing to support them for automatic differentiation purposes). Calling the two-argument
_airy
/_airyx
methods will call the three-argument_airy
/_biry
methods, but these latter methods don't seem to be defined anywhere, e.g.: