Re: Issue 2179 in sympy: Lambda refactoring

2011-05-17 Thread sympy
Updates: Status: Fixed Labels: -NeedsReview PassedReview Comment #9 on issue 2179 by ronan.l...@gmail.com: Lambda refactoring http://code.google.com/p/sympy/issues/detail?id=2179 It's in. -- You received this message because you are subscribed to the Google Groups sympy-issues

Re: Issue 2179 in sympy: Lambda refactoring

2011-04-08 Thread sympy
Comment #8 on issue 2179 by asmeurer: Lambda refactoring http://code.google.com/p/sympy/issues/detail?id=2179 Cool! I didn't know you could sympify lambdas. I guess the tuple change is OK. I don't think very many people use Lambda (despite it being a somewhat useful function). -- You

Re: Issue 2179 in sympy: Lambda refactoring

2011-04-07 Thread sympy
Comment #7 on issue 2179 by ronan.l...@gmail.com: Lambda refactoring http://code.google.com/p/sympy/issues/detail?id=2179 There's another change in my branch that I should have mentioned before: The arguments of the Lambda must now be wrapped in an iterable, so Lambda(x, y, x*y) must now be

Re: Issue 2179 in sympy: Lambda refactoring

2011-04-05 Thread sympy
Updates: Labels: NeedsReview Comment #5 on issue 2179 by ronan.l...@gmail.com: Lambda refactoring http://code.google.com/p/sympy/issues/detail?id=2179 https://github.com/sympy/sympy/pull/194 -- You received this message because you are subscribed to the Google Groups sympy-issues

Re: Issue 2179 in sympy: Lambda refactoring

2011-04-05 Thread sympy
Updates: Labels: Ronan.Lamy Comment #6 on issue 2179 by asmeurer: Lambda refactoring http://code.google.com/p/sympy/issues/detail?id=2179 (No comment was entered for this change.) -- You received this message because you are subscribed to the Google Groups sympy-issues group. To post

Re: Issue 2179 in sympy: Lambda refactoring

2011-02-08 Thread sympy
Comment #4 on issue 2179 by ronan.l...@gmail.com: Lambda refactoring http://code.google.com/p/sympy/issues/detail?id=2179 This method would be useless. If you want to curry Lambda((x, y), x+y), just use Lambda(y, x+y). -- You received this message because you are subscribed to the Google

Issue 2179 in sympy: Lambda refactoring

2011-02-07 Thread sympy
Status: Started Owner: ronan.l...@gmail.com Labels: Type-Defect Priority-Medium New issue 2179 by ronan.l...@gmail.com: Lambda refactoring http://code.google.com/p/sympy/issues/detail?id=2179 There are a few issues with Lambda which complicate the code for little benefit: * Lambda subclasses

Re: Issue 2179 in sympy: Lambda refactoring

2011-02-07 Thread sympy
Issue 2179: Lambda refactoring http://code.google.com/p/sympy/issues/detail?id=2179 This issue is now blocking issue 2178. See http://code.google.com/p/sympy/issues/detail?id=2178 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred

Re: Issue 2179 in sympy: Lambda refactoring

2011-02-07 Thread sympy
Comment #1 on issue 2179 by asmeurer: Lambda refactoring http://code.google.com/p/sympy/issues/detail?id=2179 1. So what should the class structure look like? 2. I don't understand what you are saying here. 3. I agree. -- You received this message because you are subscribed to the Google

Re: Issue 2179 in sympy: Lambda refactoring

2011-02-07 Thread sympy
Comment #2 on issue 2179 by ronan.l...@gmail.com: Lambda refactoring http://code.google.com/p/sympy/issues/detail?id=2179 1. For now, Lambda should just subclass Expr. If there is progress on issue 1688, Lambda should share code with the class of function objects. 2.

Re: Issue 2179 in sympy: Lambda refactoring

2011-02-07 Thread sympy
Comment #3 on issue 2179 by asmeurer: Lambda refactoring http://code.google.com/p/sympy/issues/detail?id=2179 OK. So I guess the curry code should be moved into a .curry() method that is not called automatically. -- You received this message because you are subscribed to the Google Groups