Filipe

@seth-p that recipe is only to test the Windows build and not for user use. Why do you need to that for? I recommend you to go for the conda-forge...

@seth-p that is the conda-forge build. The repository responsible for that is https://github.com/conda-forge/netcdf4-feedstock That pinning is required for that specific build. We (conda-forge) need to pin software to ensure compatibility...

> The Windows binaries at https://pypi.python.org/pypi/netCDF4/ are using hdf5-1.10.1 and netcdf4-4.4.1.1 Interesting. I'll double check that. I remember trying hdf5 1.10 and having issues with that.

I'm not familiar with wheels but I found `libnetcdf-60d928ce.so.18.0.0` when unpacking the wheel. Not sure what is going.

Thanks. I'll test it as soon as it is out.

I forgot about this one but it looks like the latest wheel is using `libnetcdf-9e49a1ce.so.19`.

BTW, the screenshots in https://github.com/Unidata/netcdf4-python/issues/1179#issuecomment-1202720571 make it hard to read about the real issue. It seems that the problem is with curl and some SSL certificates. I get this when...

It may be a version problem or something with the wheel build. I guess the only way to figure this out is to add an OPeNDAP test during the wheel...

I believe that the wheel should be rebuilt. One test folks could try is to conda install it on colab and see if that works.

@sgdecker if I just read this issue quickly and it seems that the issues are all on Windows, right? I'll try to get a Windows machine and test it. Note...