h5py version pin

[kafitzgerald]

This h5py version pin is likely to create environment problems for folks. I think we can probably work around it for the E2S implementation, but it's likely to pop up as an issue elsewhere.

miles-credit/pyproject.toml

Line 18 in 1b26dd9

"h5py<=3.14.0",

It looks like this was introduced here due to some compatibility issues between netcdf4 and h5py when installed from PyPI: #246 (comment)

And there may have since been some progress on addressing the issue upstream (though it's not clear what exactly the current state is): Unidata/netcdf4-python#1438

[djgagne]

Based on the end of the thread, it looks like netcdf4-python might fix this issue in their next release, but it's not clear when that will come. Since netcdf4-python appears to be slower releasing than h5py, and h5py plays nicely with netcdf4 v1.7.2 should I switch the version pin to netcdf4 instead and update once the new netcdf4 comes out?

[kafitzgerald]

Based on the end of the thread, it looks like netcdf4-python might fix this issue in their next release, but it's not clear when that will come. Since netcdf4-python appears to be slower releasing than h5py, and h5py plays nicely with netcdf4 v1.7.2 should I switch the version pin to netcdf4 instead and update once the new netcdf4 comes out?

Yeah, I think that might be a bit better / clearer. Something like this:
"netCDF4<1.7.3", # https://github.com/Unidata/netcdf4-python/issues/1438

Ideally this gets addressed upstream though and we can remove the pin(s). Bummer about the release schedule.

On second glance, I don't think this will be quite as problematic as I'd initially thought, but still would be nice to resolve.