Comment #2 on issue 3560 by [email protected]: solve() is a giant mess http://code.google.com/p/sympy/issues/detail?id=3560
I'm not sure if that will simplify things much, though I still think we should do it (or is it really just better eval_inverse support that we need?). Mul._eval_solve would be trivial, but Add._eval_solve would be basically the whole solving code. The variation of different kinds of expressions isn't really expressed in the core classes.
On the other hand, I like how dsolve is structured (there are some things that could be changed, but the basic idea is pretty extensible).
-- You received this message because you are subscribed to the Google Groups "sympy-issues" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sympy-issues?hl=en.
