In the current implementation nata.utils.attrs.attrib_equality() uses a hack
to check if equality of two objects based on attributes defined with attr.
While it works out and fulfills it's purpose, it seems a little bit hacky. In
particular, the part were attributes with attr.ib(..., eq=True, ...) are
actually only considered. I think we should use a custom dunder method to
specify how objects are checked. If this exist in an object, then this will be
considered. Otherwise we check for equality between the objects.
In the current implementation
nata.utils.attrs.attrib_equality()
uses a hack to check if equality of two objects based on attributes defined withattr
. While it works out and fulfills it's purpose, it seems a little bit hacky. In particular, the part were attributes withattr.ib(..., eq=True, ...)
are actually only considered. I think we should use a custom dunder method to specify how objects are checked. If this exist in an object, then this will be considered. Otherwise we check for equality between the objects.