Acquisition wrappers do not respect equality/ordering of the base object

[d-maurer]

Unless a class defines __cmp__ (which is unusual for Python 3), acquisition wrappers ignore equality and ordering definitions for the base object and implement them based on the base object's addresses.

>>> from Acquisition.tests import I
>>> class RichOrdered(I):
...   def __eq__(self, other): return self.id == other.id
...   def __lt__(self, other): return self.id < other.id
... 
>>> i1 = RichOrdered(""); i2 = RichOrdered("")
>>> top = I(""); top.i1 = i1; top.i2 = i2
>>> i1 == i2
True
>>> top.i1 == top.i2
False
>>> i2.id = "i2"
>>> i1 < i2
True
>>> top.i1 < top.i2
False

[icemac]

Does this happen both in the C implementation and the Python one?

[d-maurer]

Michael Howitz wrote at 2021-7-19 23:01 -0700:

Does this happen both in the C implementation and the Python one?

At least, a source comment (in the Python implementation) says so.