Comment:

A user of the conda-forge esmpy recently opened a support ticket with the ESMF team because they were unable to write a NetCDF regridding weights file from the esmpy version they had installed because it was not built with PIO (the Parallel IO library) support. We found that the issue was that they were using a nompi version of the conda-forge esmpy package – and nompi implies no PIO, and thus no ability to write NetCDF regridding weight files (or to read certain NetCDF files).

I am adding documentation about this in the ESMPy documentation (esmf-org/esmf#130), but I wondered if any notes should be made about this in the conda-forge documentation of this package? It looks like there are nompi as well as mpi builds of esmpy for any given architecture / OS. I'm not familiar enough with conda to understand when a user will get one vs. the other, but maybe this can be clarified?