Closed larsevj closed 3 weeks ago
We quite often use np.float32, so I am not sure if this is correctly typed.
I will check if it is possible to be more spesific, np.float_
is in any case just a deprecated alias for np.float64 -> np.double
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 86.61%. Comparing base (
091a179
) to head (823a6b6
). Report is 11 commits behind head on main.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
If it should work with both 32-bit and 64-bit there is np.floating
.
np.floating[Any]
does not seem to work with python3.8, so a bit unsure what do to about the more general instances.
You can use from __future__ import annotations
to have the types only be interpreted when mypy runs. mypy runs using python 3.12.
I believe trying to figure out which function/variable is allowed/might be float32 vs float64 is a bigger task and might better have its own issue(?). This change (PR) will only bring into light the fact that we might not have typed hint correctly before?
When applicable