[sage-devel] Re: Sage 4.4.4 doctest failure on Mac PPC

2010-06-29 Thread kcrisman
Thanks, Georg, for clarifying that it's Tiger, not PPC. This ticket is already open at http://trac.sagemath.org/sage_trac/ticket/9361, and I will change it accordingly. - kcrisman On Jun 29, 3:26 am, "Georg S. Weber" wrote: > On 29 Jun., 04:04, Mike Hansen wrote: > > > On Mon, Jun 28, 2010 at

[sage-devel] Re: Sage 4.4.4 doctest failure on Mac PPC

2010-06-29 Thread Georg S. Weber
On 29 Jun., 04:04, Mike Hansen wrote: > On Mon, Jun 28, 2010 at 3:07 PM, Georg S. Weber > > wrote: > > I remember that once Michael Abshoff had created some mechanism to > > make the Sage/Maxima interface (i.e. the pexpect interface in general) > > produce verbose output into some log files (vi

Re: [sage-devel] Re: Sage 4.4.4 doctest failure on Mac PPC

2010-06-28 Thread Mike Hansen
On Mon, Jun 28, 2010 at 3:07 PM, Georg S. Weber wrote: > I remember that once Michael Abshoff had created some mechanism to > make the Sage/Maxima interface (i.e. the pexpect interface in general) > produce verbose output into some log files (via setting an enironment > variable?), but I didn't ge

[sage-devel] Re: Sage 4.4.4 doctest failure on Mac PPC

2010-06-28 Thread Georg S. Weber
On 28 Jun., 19:28, kcrisman wrote: > I know there are not tons of PPC users still on these lists, but I > wanted to ask whether they had seen something weird when testing sage/ > interfaces/maxima.py.  Namely, there is a guaranteed timeout (even > with SAGE_TIMEOUT=1)!  Previously I traced t