Changing array dtype to float
Thanks looks good to me, you could add an integer unit test.
I think using float64 is the right thing for stats. I don't know if anyone would want to use low precision with float32 for this but I would think that's unlikely.
However, for machines that can handle it correctly, we could leave higher precision than float64 unchanged. (I never checked and I think on Windows float96 doesn't do anything better than float64).
There are some tougher NIST test cases that f_oneway cannot handle in float64 without rescaling or shifting the data by the user, IIRC.
@rgommers A simple fix that should be quite innocent, I add 0.14 milestone. Reset to 0.15 if it's too late.
Adding a test of stats.f_oneway on uint16 array with large integer va…
Coverage remained the same when pulling 47016ac on ankit-maverick:issue3376 into 4b4620b on scipy:master.
@josef-pkt we're really overdue and this isn't critical, so pushing to 0.15.0
Merge branch 'pr/3416' into master.
Reviewed at #3416
Pushed with some minor style changes as fb99db7. Thanks Ankit, Josef.