Jeff Whitaker

[stubtest](https://github.com/Unidata/netcdf4-python/actions/runs/9686631247/job/26732005277?pr=1302) is failing

> > [stubtest](https://github.com/Unidata/netcdf4-python/actions/runs/9686631247/job/26732005277?pr=1302) is failing > > Can you try again please? still failing

waiting for @RandallPittmanOrSt to complete his review

@headtr1ck what is the procedure for updating this when a new function is added to the API (for example, PR #1348)?

Can you be more specific about the problem you mentioned ("spams megabytes worth of warnings")? We can hopefully fix that in the pre-built wheels.

@bluppfisk what modules were imported by the script that produced these warnings? I suspect a binary incompatibility between HDF5 versions included in netCDF4 and some other package (perhaps xarray or...

the multiprocessing bit may be the culprit - the netCDF4 and HDF5 libs are not thread-safe.

agreed - it's not likely a threading issue then. How was the xarray package installed? via conda, pip, or a locally built wheel? I'm guessing it's using a different version...

The CI tests did not fail - so I guess we don't have a numpy 2.0 compatibility problem after all?

how about using the approach in https://github.com/Unidata/netcdf4-python/pull/1317/files? (still use oldest-supported-numpy for python < 3.9)