Following the decision from #2599, we need to _implement_ the approach we decide on
Reference:
cube-arithmetic feature branch merge back to master)cube-arithmetic-docs feature branch merge back to master)AncillaryVariables and CellMeasures from resultant cubemetadata rename to signature ? @pp-mo circular is part of DimCoord metadataDimCoordMetadata, AuxCoordMetadata and CoordMetadata (common parent) supportDimCoord and AuxCoordname vs identity __eq__, combine and difference<container>.metadata setter/getter patternswhatsnew entryNot sure whether some of these may get pulled into the _core deliverables_...
iris.cube.Cube.coordsiris.cube.Cube.replace_coordiris.cube.Cube.remove_coordnamedtuple derived classes:lru_cache for optimised LUT metadata generation~attributescoord_systemBaseMetadata class hierarchy_BaseMeta metaclass< support of Noneiris.coords._DimensionalMetadata._is_defn -> iris.coords._DimensionalMetadata.metadata (BaseMetadata)iris.coords.AncillaryVariable.metadata (BaseMetadata)iris.coords.CellMeasure._as_defn -> iris.coords.CellMeasure.metadata (CellMeasureMetadata)iris.coords.Coord._as_defn -> iris.coords.Coord.metadata (CoordMetadata)iris.iterate._CoordWrapper._as_defn -> iris.iterate._CoordWrapper.metadata (CoordMetadata)iris.aux_factory.AuxCoordFactory._as_defn -> iris.aux_factory.AuxCoordFactory.metadataSTASH only specific to iris.cube.Cubename() methodnames propertyiris.cube.Cube.is_compatibleiris.coords.Coord.is_compatibleiris.util.as_compatible_shapeiris.util.describe_diff2.3.0:~future switch for new arithmetic~whatsnew entry~iris.coords._DimensionalMetadata to ...iris.analysis._dimensional_metadata_comparison to ...STASH to stash in Names namedtuple~iris.core with associated re-organisationcircular from DimCoord equality and make it a calculated @property~STASH/GRIB_CODE~@lenient_client and @lenient_service on same function/methodRef #1911
See PR #3558
Closed by #3785
Most helpful comment
Closed by #3785