Closed DStauffman closed 1 year ago
Hi @DStauffman. This was fixed in #1176. There will be a new release of datashader
soon incorporating this fix, when we have dealt with all the other issues relating to today's release of numba 0.57
(e.g. https://github.com/holoviz/datashader/pull/1205). In the meantime if you pin either numba<0.57
or numpy<1.24
it should all work OK.
Any ETA for the release? Numpy 1.24 is already quite old, this could (should) be a bugfix release that does not wait for all the issues in the v0.14.5 milestone.
There is a dev release 0.14.5a1 out on PyPI (https://pypi.org/project/datashader/0.14.5a1/) and the pyviz/label/dev
conda channel (https://anaconda.org/pyviz/datashader/files).
The timing of numpy 1.24 isn't relevant, it is the timing of the numba release that supports numpy 1.24. That was 0.57 which was released 2 weeks ago.
Right, I did not notice the pre-release! Thanks for handling the numba changes.
ALL software version info
Description of expected behavior and the observed behavior
In datashader\core.py, function bypixel throws an error with the np.warnings command:
Seems to be fine in older versions of numpy. I'm not sure if this is now expected behavior that needs to be adapted or if it's an upstream bug in numpy.