Status: Accepted
Owner:
Labels: Type-Defect Priority-Medium
New issue 2809 by asmeu...@gmail.com: evalf() doesn't go all the way
http://code.google.com/p/sympy/issues/detail?id=2809
In [53]: 2*pi*I*(cos(k*abs(a)*I)/(2*abs(a)*I*(b**2 - a**2)) +
cos(k*abs(b)*I)/(2*abs(b)*I*(a**2 - b**2))).s
Updates:
Status: Duplicate
Mergedinto: 1583
Comment #1 on issue 2809 by smi...@gmail.com: evalf() doesn't go all the way
http://code.google.com/p/sympy/issues/detail?id=2809
(No comment was entered for this change.)
--
You received this message because you are subscribed to the
Updates:
Status: Accepted
Mergedinto:
Comment #2 on issue 2809 by asmeu...@gmail.com: evalf() doesn't go all the
way
http://code.google.com/p/sympy/issues/detail?id=2809
I'm not 100% convinced that that's the same issue. The expression in issue
1583 doesn't even evaluate co
Updates:
Status: Invalid
Comment #3 on issue 2809 by smi...@gmail.com: evalf() doesn't go all the way
http://code.google.com/p/sympy/issues/detail?id=2809
The problem here is that only one factor of the Mul is being evalf'ed:
>>> pi*(3*x).n()
3.0*pi*x
>>> (pi*(3*x)).n()
Comment #4 on issue 2809 by asmeu...@gmail.com: evalf() doesn't go all the
way
http://code.google.com/p/sympy/issues/detail?id=2809
Wow, I feel really stupid. This is why you should assign things to
variables and manipulate the variables, rather than trying to keep nesting
function and m
