Comment #97 on issue 1694 by Vinzent.Steinberg: solve has many issues with fractions
http://code.google.com/p/sympy/issues/detail?id=1694
What sort of approaches do you envision for solve strategies that would give different results?
Well, either we get solve() to always return the best result and be fast anyway, or we have to accept that there are different approaches with mixed, unpredictable results, like it is the case for dsolve(), in which case the user has to decide what he wants.
For examples, see the approaches Nicolas proposed. Factoring before solving could be another strategy.
How could sympy decide that [sol1] is better thant [sol2]?
Aaron implemented metrics for this, which are already used by dsolve. I think it mixes several approaches, but also counting operations.
-- 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.
