Open peytondmurray opened 1 month ago
As I mentioned above, I can reproduce with 3.11.0 but as of h5py commit 2c80981022e741a04e02d4afd6ae78bac1bc770f
the error is gone and everything works as intended. I can't yet tell if this is again some kind of cython/typing issue, but one thing to note is that it is probably not necessary to call into the underlying hdf5 library to get the virtual filename - the dcpl
object passed into the build_data_dict
function where the issue is happening is a PropDCID
type with a pure-Cython .get_virtual_filename
function, with the only call into Python code being the allocation of a bytes
object. So I doubt if we would lose much if we just call into that function instead.
Likely related to #352 - the following is broken on Linux (but not Mac) with the latest commit on
master
:With
h5py==3.11.0
I get the following: