Source: python-pynndescent
Version: 0.5.8-2
Severity: normal
Control: block 1061605 by -1
python-pynndescent is failing test_distances with scipy 1.11 from experimental
103s else:
103s > raise ValueError('Unknown Distance Metric: %s' % mstr)
103s E ValueError: Unknown Distance Metric: kulsinski
103s
103s /usr/lib/python3/dist-packages/scipy/spatial/distance.py:2230: ValueError
103s =============================== warnings summary
===============================
103s pynndescent/tests/test_distances.py: 13 warnings
103s /usr/lib/python3/dist-packages/numba/np/ufunc/array_exprs.py:301:
DeprecationWarning: ast.Num is deprecated and will be removed in Python 3.14;
use ast.Constant instead
103s return ast.Num(expr.value), {}
103s
103s -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
103s =========================== short test summary info
============================
103s FAILED
../build.PmL/src/pynndescent/tests/test_distances.py::test_binary_check[kulsinski]
103s FAILED
../build.PmL/src/pynndescent/tests/test_distances.py::test_sparse_binary_check[kulsinski]
103s ============ 2 failed, 33 passed, 14 skipped, 13 warnings in 21.58s
============
scipy 1.11 is currently in experimental but I'd like to upload soon to
unstable to resolve Bug#1061605, which would make this bug serious.
Looks like it's been fixed in the latest release of pynndescent.
