The netcdf4 package on conda-forge recently dropped python 3.10 support (conda-forge/netcdf4-feedstock#186) in order to build one package for python >=3.11 with ABI 3.
This means that MPAS-Tools will need to drop python 3.10 in order to keep in sync with the conda-forge package ecosystem. I have already had to do this in the conda-forge recipe in conda-forge/mpas_tools-feedstock#149. We may as well do it here as well.
While we're at it, we should sync up the dependencies in https://github.com/MPAS-Dev/MPAS-Tools/tree/master/conda_package/ci with the equivalents on conda-forge in https://github.com/conda-forge/mpas_tools-feedstock/tree/main/.ci_support. No need to worry about hdf5 2.x.x yet, thought.
The netcdf4 package on conda-forge recently dropped python 3.10 support (conda-forge/netcdf4-feedstock#186) in order to build one package for python >=3.11 with ABI 3.
This means that MPAS-Tools will need to drop python 3.10 in order to keep in sync with the conda-forge package ecosystem. I have already had to do this in the conda-forge recipe in conda-forge/mpas_tools-feedstock#149. We may as well do it here as well.
While we're at it, we should sync up the dependencies in https://github.com/MPAS-Dev/MPAS-Tools/tree/master/conda_package/ci with the equivalents on conda-forge in https://github.com/conda-forge/mpas_tools-feedstock/tree/main/.ci_support. No need to worry about hdf5 2.x.x yet, thought.