On Jan 15, 2010, at 8:18 AM, mindcorrosive wrote: > I've reinstalled python with sympy (cleaning up everything in the > install directory in between), and the issue still occurs. Upgrading > to a more recent Python version is not an option -- I'm developing a > plugin for a certain application that has embedded Python scripting > engine -- and they use Py2.4. Still, I've tested the latest sympy and > Py2.6 and it works as it should on the same machine. > > I did some additional tests and it seems that the crux is in the evalf > method -- other similar functions, like sin and log, are also affected > in the same way, and the a.evalf() (see code sample for "a") method > does not work as it should as well. > > Sympy versions 0.6.1 and 0.6.0 work properly, although 0.6.5, 0.6.4 > and 0.6.2 (and most likely 0.6.3 as well) do not (yes, I've tested > them all, and yes, I'm that desperate). What about sympy 0.6.6?
Also, since it seems to have worked before, could you use git to bisect the source to find the offending commit. Here is a little tutorial in case you don't know git. You will probably need msysgit or some similar. Just do: git clone git://git.sympy.org/sympy.git # This downloads the repository, including the whole history. git bisect start # This starts the bisect process git checkout sympy-0.6.4 # The first version that doesn't work git bisect bad # Set it as bad git checkout sympy-0.6.3 # The latest version that does work git bisect good # Set it as good At this point, git will checkout a commit somewhere in between the two versions. It should give you a good guide as you go. In each case, run check if it works by running isympy in the bin directory and type git bisect good or git bisect bad accordingly until it tells you what the first offending commit is. Then please paste the SHA1 of that offending commit here (git show SHA1 will show you what changed with that commit). Hopefully this will provide more insight to help fix this. Aaron Meurer > > At this stage I'm pretty convinced it's a bug. Perhaps it's platform- > specific (I'm running WinXP SP3)? It works properly in linux (I've > tested it myself in Ubuntu 9.10 in a VM w/ Py2.4 and sympy 0.6.4 from > source). > > I understand that I'm apparently the only one having this issue, but > that doesn't mean it's not there. I'm willing to provide you with all > the debugging help that you need, should you decide to look deeper > into this (it's a rather critical issue for me, and I don't want to go > back to ancient sympy versions -- I use sympy.mpmath.optimization > which apparently is not present in 0.6.1). > > I'm welcome to any suggestions. Thanks for the understanding. > > On Jan 14, 7:24 pm, Aaron Meurer <[email protected]> wrote: >> I just tried all sympy versions back to 0.6.3 in Python 2.4.4 and they all >> worked fine. >> >> Perhaps you should try reinstalling sympy and/or Python. I would recommend >> upgrading to Python 2.5 or 2.6 anyway. >> >> Aaron Meurer >> On Jan 14, 2010, at 4:18 AM, smichr wrote: >> >>> I don't have 2.4.4 but 2.4.2 and 2.5.4 and 2.6.4 are all working for >>> me: >> >>> PythonWin 2.6.4 (r264:75708, Oct 26 2009, 08:23:19) [MSC v.1500 32 bit >>> (Intel)] on win32. >>> Portions Copyright 1994-2008 Mark Hammond - see 'Help/About PythonWin' >>> for further copyright information. >>>>>> import sympy as sy >>>>>> float(sy.exp(10)+sy.exp(20)) >>> 485187221.87558508 >> >>> Python 2.5.4 (r254:67916, Dec 23 2008, 15:10:54) [MSC v.1310 32 bit >>> (Intel)] on >>> win32 >>> Type "help", "copyright", "credits" or "license" for more information. >>>>>> import sympy as sy >>>>>> float(sy.exp(10)+sy.exp(20)) >>> 485187221.87558508 >>>>>> ^Z >> >>> Python 2.4.2 (#67, Sep 28 2005, 12:41:11) [MSC v.1310 32 bit (Intel)] >>> on win32 >>> Type "help", "copyright", "credits" or "license" for more information. >>>>>> import sympy as sy >>>>>> float(sy.exp(10)+sy.exp(20)) >>> 485187221.87558508 >> >>> /c >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "sympy" 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 >>> athttp://groups.google.com/group/sympy?hl=en. >> >> > -- > You received this message because you are subscribed to the Google Groups > "sympy" 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?hl=en. > >
-- You received this message because you are subscribed to the Google Groups "sympy" 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?hl=en.
