#9361: Maxima timeout on Mac OS X 10.4 (Tiger)
------------------------+---------------------------------------------------
   Reporter:  kcrisman  |          Owner:  tbd           
       Type:  defect    |         Status:  needs_review  
   Priority:  critical  |      Milestone:  sage-4.8      
  Component:  packages  |       Keywords:                
Work_issues:            |       Upstream:  N/A           
   Reviewer:            |         Author:  Jeroen Demeyer
     Merged:            |   Dependencies:                
------------------------+---------------------------------------------------

Comment(by kcrisman):

 > > How did this change from minor to critical?
 > I think a patch which adds a new platform to the list of completely
 supported platforms warrants being "critical".  But that's just my
 opinion.
 >
 > > There is nothing wrong with tab completion on that platform AFAIR,
 just this timeout.
 > That's why I changed the ticket title.  I guess somebody discovered the
 timeout in `maxima.py` and somehow mistakenly assumed it was because of
 TAB completion.  Or, in an earlier version there was a problem was TAB-
 completion on OS X 10.4 which is now fixed.

 I see, the answer to both are the same.  I should clarify: as far as I
 could determine when I filed this ticket, it was precisely the tab-
 completion doctest which caused the timeout, but not because tab-
 completion didn't work, it just didn't doctest well.  Hence the minor and
 mention of tabs.

 > > Are there any problems we might expect from this change, such as
 interrupts not working as quickly for Maxima on other (newer) platforms?
 > Assuming that interrupts in Maxima are implemented properly (admittedly,
 a big "if"), there should not be any change in existing behaviour.  If the
 interrupt works properly, the changed timeout doesn't matter.
 >
 > This patch does not change the interrupt behaviour of Maxima itself, it
 only changes how often Sage sends interrupts to Maxima.  On OS X 10.4,
 Maxima can be interrupted, it is just slow, which makes Sage think that
 something is wrong.

 Right.

 I'll try this when I get a chance - which won't be immediately, still
 recovering from SD35.5 and an accident incurred during that time.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9361#comment:7>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" 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/sage-trac?hl=en.

Reply via email to