Drew Parsons a écrit le 03/04/2020 à 15:08 : > 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).
Nope. Seems related to the h5py 'serial' flavour only. It appears for the first time when you configure the build for both flavours. If I force the 'mpi' flavour installation *without* the 'serial' one, bitshuffle builds fine. _g.
signature.asc
Description: OpenPGP digital signature
