Closed hugobuddel closed 1 year ago
Oh, the new test is not directly related, but was an attempt to reproduce the problem (which didn't work). But well, it probably adds a little bit of coverage.
Patch coverage: 66.66%
and project coverage change: +0.29%
:tada:
Comparison is base (
3e0a825
) 78.50% compared to head (889bb1c
) 78.80%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
These checks were broken anyway, because they only checked for float, while the values where actually numpy.float64. As a result, many functions returned an an array with a single element. This array then got silently converted to a float anyway, but this will change, as this warning is emitted:
DeprecationWarning: Conversion of an array with ndim > 0 to a scalar is deprecated, and will error in future. Ensure you extract a single element from your array before performing this operation. (Deprecated NumPy 1.25.)
isintance will return True for both float and numpy.float64, so now everything will work as intended.
Also removing a mutable array from a function definition.