Pin xgcm version

[VeckoTheGecko]

Description

xgcm/xgcm#743 resulted in the dropping of Axis from the public API hence we can't use it for typechecking. We'll very likely drop xgcm entirely before release, so just pinning for now.

Checklist

• Closes None
• This PR targets the correct branch (main for normal development, v3-support for v3 support)

AI Disclosure

None

[hdrake]

@VeckoTheGecko , it is removed from the top-level public API but can't you still use it like this?

from xgcm.axis import Axis

[hdrake]

Also, can you point me towards an Issue/Discussion/PR that discusses dropping xgcm entirely? What is the reason for this? Helpful for me to know why xgcm is or is not serving community needs!

[VeckoTheGecko]

Hi @hdrake . We only used xgcm for the parsing of the COMODO/SGRID metadata conventions. Due to a bug in xgcm's parser (xgcm/xgcm#686 ) we now we have our own SGRID parsing ( #2418 ) which is more reliable and maintainable than the logic in xgcm. After some refactoring, xgcm will become an unused dependency.

Deepak and Julius flagged interest in xgcm/xgcm#686 about adding SGRID to cf_xarray (or an xarray-sgrid package) so its more interoperable. Our sgrid module is intentionally quite orthogonal, and can be easily lifted into a different package at some point for those interested in doing so.