You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tests, specifically a couple of them contained in a docstring from the _py_algorithms.py file, are failing due to the representation numbers.
Numpy 2.x introduced changes in the representation of scalars. Therefore, instead of having a clear output like you would without numpy, the output now also includes 'np.float64', for example.
The most logical solution is to update the representation of those scalars. Forcing the tests to use numpy < 2.x should also work as a temporary fix.
To Reproduce
The code block below should produce no errors if numpy < 2.x is used but fail if 2.x is used.
Describe the bug
Tests, specifically a couple of them contained in a docstring from the _py_algorithms.py file, are failing due to the representation numbers.
Numpy 2.x introduced changes in the representation of scalars. Therefore, instead of having a clear output like you would without numpy, the output now also includes 'np.float64', for example.
The most logical solution is to update the representation of those scalars. Forcing the tests to use numpy < 2.x should also work as a temporary fix.
To Reproduce
The code block below should produce no errors if numpy < 2.x is used but fail if 2.x is used.
Expected behavior
The tests should pass since the scalars are correct.
Screenshots
From the CI/CD run of #167
Environment (please complete the following information):
Additional context
The relevant numpy changes are described here: https://numpy.org/devdocs/release/2.0.0-notes.html#representation-of-numpy-scalars-changed
The text was updated successfully, but these errors were encountered: