Comment #5 on issue 2246 by ronan.l...@gmail.com: Global directive to switch strict transformations
http://code.google.com/p/sympy/issues/detail?id=2246
Having a global switch is always a bad idea, I think. Such things tend to cause a lot of trouble. Even as an option, turning it on would cause a lot of wrong results to be returned. But actually, "nonstrict computation" is already the default and wrong results are returned at present, for example solve(sin(x), x) -> [0].
Anyway, concerning the examples above, strict vs nonstrict isn't the issue. tan(atan(x)) is always equal to x, so atan(x) = y always implies x = tan(y).
-- You received this message because you are subscribed to the Google Groups "sympy-issues" group. To post to this group, send email to sympy-issues@googlegroups.com. To unsubscribe from this group, send email to sympy-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sympy-issues?hl=en.
