Comment #4 on issue 2246 by [email protected]: Global directive to
switch strict transformations
http://code.google.com/p/sympy/issues/detail?id=2246
Sure they could. But still it will be better to divide this problem into
two subproblems (it could be one issue):
1st - change standard and special functions to be able to call inverse
(using some cut agreements) if the keyword nonstrict or may be foliation or
whatever are set to true.
2nd - do what you say in previous comment.
The profit of such differentiation is that the other functions like evalf
will be able to use nonstrict computation, so the functionality won't be
doubled for any function that need it (and this will be so if we implement
it all inside solve function).
Anyway I will be glad to help.
--
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.
