Nice, Ondrej! Thanks for spending time on this!
I remember at one point implementing a trivial .doit() to prevent a
crash further up. I was not that familiar with the code at the time, so
I didn't want to mess around with the core. It should ideally be
removed.
Øyvind
sø., 29.11.2009 kl.
2009/11/30 Aaron S. Meurer asmeu...@gmail.com
Where are you getting these examples? This one still works the same for me
in both:
import sys
import sympy
sys.maxint
9223372036854775807
x = sympy.Symbol('x')
r = sympy.solve(x**4 - 6*x**3 + 17*x**2 - 26*x + 20, x)
r
[2 + I, 1 +
2009/11/30 Aaron S. Meurer asmeu...@gmail.com
OK, here are some things that work differently in the two platforms:
On 32-bit:
In [6]: print S((C1 + C2*x)*sin(x*sqrt(2)) + (C3 + C4*x)*cos(x*sqrt(2)))
(C1 + C2*x)*sin(x*2**(1/2)) + (C3 + C4*x)*cos(x*2**(1/2))
In [5]: print
I see in the document that using set() is proposed as being a
solution. However, this was the first thing that I tried in issue 1729
and that failed, too.
sympy.polys.rootfinding.roots_quartic
_
File C:\documents and settings\chris\sympy\sympy\polys
And here's a strange and perhaps related result. A tests that gave a
False at one point gives a True later:
C:\Documents and Settings\chris\python26\python.exe
Python 2.6.4 (r264:75708, Oct 26 2009, 08:23:19) [MSC v.1500 32 bit
(Intel)] on
win32
Type help, copyright, credits or license for more
