On Wed, Aug 27, 2008 at 12:46 PM, Fredrik Johansson <[EMAIL PROTECTED]> wrote: > > On Wed, Aug 27, 2008 at 11:56 AM, Ondrej Certik <[EMAIL PROTECTED]> wrote: >> It is sometimes slow if the nsimplify() cannot make it, so it probably >> should not be default, but it should be optional. >> >> I know many people (including myself) have burned themselves by >> writing 1/2*x**2, so this might help. > > If one is just interested in matching fractions, continued fractions > can be used. This is extremely fast. See > http://en.wikipedia.org/wiki/Continued_fraction#Best_rational_approximations > > Still, I think this is too much magic to use by default in sympify(). > And most users won't have imported division from __future__ anyway, so > it won't help when 1/2 == 0.
Yep, definitely optional. But this will improve in python 3.0. It will also fix things like x**(5/7) and many others. It will not fix more complex stuff like (1/2)**2008+(1/3)**2009, but it will fix the most common thing. This is now: http://code.google.com/p/sympy/issues/detail?id=1053 Ondrej --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to sympy@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
