DOC: Rename `*args` param in `f_oneway` to `*samples`
See original GitHub issueThe current signature for the f_oneway
function in the stats
module reads:
def f_oneway(*args, axis=0):
which does not provide any real clarity, imo.
My suggestion is to refactor the *args
param to *samples
, or *samps
—whatever form is more agreeable.
The docstring itself uses sample
:
sample1, sample2, … : array_like
Of course anyone calling this function would have an idea of what the function would accept; nevertheless, I think this would add value at zero cost (just a refactor within the function).
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
scipy.stats.f_oneway — SciPy v1.9.3 Manual
The test is applied to samples from two or more groups, possibly with differing sizes. Parameters. sample1, sample2, …array_like. The sample measurements for ......
Read more >Customize your pipeline - Azure Pipelines - Microsoft Learn
Step-by-step tutorial to customize a pipeline.
Read more >swaptomostacks
NAME swaptomostacks - Exchange tilt series files for making tomogram with same parameters · SYNOPSIS swaptomostacks -from otherRoot -to saveRoot [options] ...
Read more >Designing with Parameters in Autodesk Inventor - PDH Online
Inventor 2010 is used in this course to illustrate examples, but the concepts ... We can rename all three parameters which define the...
Read more >Effective Go - The Go Programming Language
Named result parameters. The return or result "parameters" of a Go function can be given names and used as regular variables, just like...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I would say so.
I would go with the second form
*samples : tuple of array_like
. It’s what numpydoc says.Thanks for asking! The more you test locally the better as you could limit CI usage. Still, it’s usually fine to just run the tests of the module you are touching. Of course, some functions are used in other modules and it might be disruptive. But it’s ok and the CI will catch this. Something that is more important I would say would be to skip some CI if you just change the doc for instance (cf CI doc on our dev doc).
Thanks for reporting @ShivnarenSrinivasan! Seems like a good idea and the docstrings would also need an update.
samples
seems more appropriate. We should avoid truncating words like this. Would you like to make a PR?