Closed wpbonelli closed 5 months ago
Numpy migration notes say this is expected for expressions where float32 is combined with the builtin float, this was the only one caught by a test but there are probably more cases where the change in promotion rules leads to slightly different results,. In general it may suffice to relax test comparisons but where we return non-numpy data structures (as here) it seems worth converting any np scalars to builtins for consistency
test_lgrutil.py
fails with numpy>=2.0.0rc1float()
to avoid loss of precision, per https://numpy.org/devdocs/numpy_2_0_migration_guide.html#changes-to-numpy-data-type-promotionlgr.get_exchange_data()