[sage-devel] Re: sage-2.5.alpha0 equality testing bug

2007-04-26 Thread Jonathan William Bober
lliam Stein wrote: > Thanks!! > > On 4/26/07, Jonathan William Bober <[EMAIL PROTECTED]> wrote: > > > > Never mind all that - it seems that the fix is easy. Just after > > > > symbols = {operator.lt:' < ', operator.le:' <=

[sage-devel] Re: sage-2.5.alpha0 equality testing bug

2007-04-26 Thread Jonathan William Bober
Never mind all that - it seems that the fix is easy. Just after symbols = {operator.lt:' < ', operator.le:' <= ', operator.eq:' == ', operator.ne:' != ', operator.ge:' >= ', operator.gt:' > '} maxima_symbols = dict(symbols) maxima_symbols[operator.eq] = '=' in calculus/eq

[sage-devel] sage-2.5.alpha0 equality testing bug

2007-04-26 Thread Jonathan William Bober
Unless I am misunderstanding something, 2.5.alpha0 seems to have some problems with equality testing. A typical example is sage: bool(sqrt(2) == 1) False sage: bool(sqrt(2) != 1) False However, the following does work correctly: sage: bool(sqrt(2) < 1) False sage: bool(sqrt(2) > 1) True This s

[sage-devel] Re: sage-2.5.alpha0

2007-04-23 Thread Jonathan William Bober
It also builds fine for me under Ubuntu Edgy Eft, on an Intel Core Duo. Like others have reported, the only doctest failures seem to be in multi_polynomial_libsingular.pyx. On Mon, 2007-04-23 at 02:35 -0700, William Stein wrote: > Hi, > > I've posted a preliminary SAGE-2.5.alpha0 tarball here: