Hi all, On 2013-02-17, Simon King <simon.k...@uni-jena.de> wrote: > OK. That's indeed an argument to make it possible to override > stuff---users are supposed to know what they do.
I just posted a new patch version at #14054. It is more pythonic in the sense that it allows for overloading hash and rich comparison. One question remains: In the current patch version, if you do class MyClass(UniqueRepresentation, MyBaseClass) then *rich* comparison and hash inherited from MyBaseClass will be overridden. However, *comparison* inherited from MyBaseClass will not be overridden. Hence, you may have instance a,b of MyClass with the following properties: sage: a == b False sage: hash(a) == hash(b) False sage: cmp(a,b) 0 Here I am not sure: Must hash be compatible with cmp or with rich comparison? Hence, should I overload __cmp__ as well? Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
