Re: Issue 2738 in sympy: Make a distinction between operations and their result

Issue 2738: Make a distinction between operations and their result http://code.google.com/p/sympy/issues/detail?id=2738 This issue is now blocking issue sympy:274. See http://code.google.com/p/sympy/issues/detail?id=274 -- You received this message because you are listed in the owner or CC field

Re: Issue 2738 in sympy: Make a distinction between operations and their result

Comment #8 on issue 2738 by asmeu...@gmail.com: Make a distinction between operations and their result http://code.google.com/p/sympy/issues/detail?id=2738 OK, another question, which came up on the mailing list. Should OpAdd(OpAdd(x, y), z) == OpAdd(x, OpAdd(y, x))? Also, what happens if

Re: Issue 2738 in sympy: Make a distinction between operations and their result

Comment #7 on issue 2738 by ronan.l...@gmail.com: Make a distinction between operations and their result http://code.google.com/p/sympy/issues/detail?id=2738 The answer to both questions is clearly no. x + y and y + x print differently, so they should be different. -- You received this me

Re: Issue 2738 in sympy: Make a distinction between operations and their result

Comment #6 on issue 2738 by asmeu...@gmail.com: Make a distinction between operations and their result http://code.google.com/p/sympy/issues/detail?id=2738 Another thing to consider is the ordering of args (for commutative operations). Should x + y and y + x be automatically canonicalized

Re: Issue 2738 in sympy: Make a distinction between operations and their result

Issue 2738: Make a distinction between operations and their result http://code.google.com/p/sympy/issues/detail?id=2738 This issue is now blocking issue 747. See http://code.google.com/p/sympy/issues/detail?id=747 -- You received this message because you are listed in the owner or CC fields of t

Re: Issue 2738 in sympy: Make a distinction between operations and their result

Comment #4 on issue 2738 by ronan.l...@gmail.com: Make a distinction between operations and their result http://code.google.com/p/sympy/issues/detail?id=2738 Let me go back to the beginning. The purpose of this is to kill the usage of Mul(..., evaluate=False). For that, we need to support t

Re: Issue 2738 in sympy: Make a distinction between operations and their result

Comment #3 on issue 2738 by asmeu...@gmail.com: Make a distinction between operations and their result http://code.google.com/p/sympy/issues/detail?id=2738 So you are differentiating between an unapplied OpMul and an OpMul that's been created, right? Surely you want to be able to do OpMul(

Re: Issue 2738 in sympy: Make a distinction between operations and their result

Comment #2 on issue 2738 by ronan.l...@gmail.com: Make a distinction between operations and their result http://code.google.com/p/sympy/issues/detail?id=2738 A Mul and an OpMul are very different beasts. One major difference is that OpMul can't be a subclass of Expr: it doesn't really make

Re: Issue 2738 in sympy: Make a distinction between operations and their result

Comment #1 on issue 2738 by asmeu...@gmail.com: Make a distinction between operations and their result http://code.google.com/p/sympy/issues/detail?id=2738 What would the class inheritance look like? Would Mul be a subclass of OpMul, or would they share a common superclass (other than Expr

Issue 2738 in sympy: Make a distinction between operations and their result

Status: Accepted Owner: ronan.l...@gmail.com Labels: Type-Enhancement Priority-Medium New issue 2738 by ronan.l...@gmail.com: Make a distinction between operations and their result http://code.google.com/p/sympy/issues/detail?id=2738 Supporting unevaluated operations like Mul(3, 4, evaluate=F