-
-
Notifications
You must be signed in to change notification settings - Fork 18.6k
Removed unnecessary params in cum_func #13550
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Current coverage is 84.34%@@ master #13550 diff @@
==========================================
Files 138 138
Lines 51113 51119 +6
Methods 0 0
Messages 0 0
Branches 0 0
==========================================
+ Hits 43109 43115 +6
Misses 8004 8004
Partials 0 0
|
Looks good to me! |
do need a test for this? |
Catch what? We already have tests in fact to ensure that the |
what I mean is I suspect we have more functions that have named numpy args - they work but we are specifically naming them |
AFAIU |
no my point is that there might be others that accept the dtype argument (or out) and yet are validated, but we really should remove the actual named arguments. This one was not caught, so there might be others. You might have to inspect them manually. Not sure you can tell the difference between a named arg and a kwarg once your function sees it. |
@jreback : GitHub search indicates that However, the same cannot be said with Fortunately, a GitHub search indicates that all other instances of |
ok, then lgtm. yeah the |
Picks up from #13167 by properly removing the parameters and ensuring that
numpy
compatibility has been maintained. The current test suite does a good job of checking that already, so no tests were added.Closes #13541.