Re: [sage-devel] Re: strange behavior of sage

2013-03-06 Thread Dan Drake
On Tue, 05 Mar 2013 at 03:51AM -0800, tom d wrote: > Yes, I would support such a warning; I've even led tutorials with new sage > users where defining things called 'max' or 'min' has seemed an obvious > thing to do and then minutes later been a problem as the default function > was unavailable.

[sage-devel] Re: strange behavior of sage

2013-03-05 Thread tom d
Yes, I would support such a warning; I've even led tutorials with new sage users where defining things called 'max' or 'min' has seemed an obvious thing to do and then minutes later been a problem as the default function was unavailable. On Tuesday, March 5, 2013 12:36:33 AM UTC+3, luisfe wrote

[sage-devel] Re: strange behavior of sage

2013-03-04 Thread Timo Kluck
Op maandag 4 maart 2013 22:36:33 UTC+1 schreef luisfe het volgende: > > Hi, > > Can any one enlight me about what is going on here? > > {{{ > sage: t=(1,2,3) > sage: type(t) > tuple > sage: len(t) > 3 > sage: len(t)=4 > sage: t > t > sage: type(t) > sage.symbolic.expression.Expression > }}} > It go