I remember being told to never override __eq__. In general I support this policy.
I often implement .equals when I need more mathematical equality checking. Perhaps renaming __eq__ to .equals would be better than deletion. On Thu, May 2, 2013 at 2:39 PM, Stefan Krastanov <[email protected] > wrote: > I have found a few pieces of code where `__eq__` is extended to check > for more than structural equality and this causes some routines to > fail. Am I right to revert __eq__ to checking only for structural > equality (and fixing related tests)? > > The code in question is `tensor.py` line 1318. > > -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/sympy?hl=en-US. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sympy?hl=en-US. For more options, visit https://groups.google.com/groups/opt_out.
