In article <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> wrote: >Yes. You stated it quite precisely. I believe l1==l2 should always >return True and l1==l3 should always be False. (unless l3 is reassigned >as l3=l1). Your idea of a separate operator for 'all elements have >numerically equal values at the moment of comparision' is a good one. >For want of a better name, it could be called DeepCopyEquality(a,b) and >would be equivalent to a byte-by-byte comparison of two distinct >regions in memory created by a deep copies of a and b.
The operator which works at the moment of comaprision is already there - that's what == does. If you really think there's a need for a comparision which includes dealing with aliasing, then it seems to me a python module with a set of functions for comparisions would make more sense. -- Jim Segrave ([EMAIL PROTECTED]) -- http://mail.python.org/mailman/listinfo/python-list
