On 2020-04-03 20:13, Gilles Filippini wrote:
This is not related to the ongoing hdf5 transition, but to the recent uploads of h5py >= 2.10.0-3. Before triggering the hdf5 transition I've checked that bitshuffle builds successfully. It was against h5py 2.10.0-2 by then.
The change in behaviour comes from the h5py upstream patches applied in h5py 2.10.0-3.
file_default_read_5e71c49.patch in particular is the one that updates the API, setting File() to mode='r' by default. I added the patch to deal with the H5pyDeprecationWarning we were getting, since the change was flagged as coming in from upstream anyway. In principle it just means mode needs to be added explicitly as h5py.File(filename, mode), if the required mode is not 'r'.
But it must be something else from these new h5py upstream patches that's leading to any other bitshuffle errors (the ones apart from the file-not-found error).
It's a pity the hdf5 transition and new h5py package structure came on at the same time, makes it a touch more angst-provoking working through the changes than it would otherwise be (h5py was in the NEW queue for a while, got accepted at the same time as the HDF5 transition).
Drew
