#13211: Upgrade GAP to 4.5.7
------------------------------------------------------------------+---------
       Reporter:  kini                                            |         
Owner:  tbd              
           Type:  enhancement                                     |        
Status:  closed           
       Priority:  major                                           |     
Milestone:  sage-5.6         
      Component:  packages                                        |    
Resolution:  fixed            
       Keywords:                                                  |   Work 
issues:                   
Report Upstream:  Reported upstream. Developers acknowledge bug.  |     
Reviewers:  Dmitrii Pasechnik
        Authors:  Volker Braun, Jeroen Demeyer                    |     Merged 
in:  sage-5.6.beta1   
   Dependencies:  #13123, #13579                                  |      
Stopgaps:                   
------------------------------------------------------------------+---------

Comment (by kcrisman):

 I get some weird stuff in interfaces/gap.py on OS X 10.4 with 5.6.beta2.
 Things like
 {{{
 sage: n = get_gap_memory_pool_size()
 <snip>
     free_ram = int(free_ram([:-1]) * units[free_ram[-1]]
 ValueError: invalid literal for int() with base 10: '33.1'
 }}}
 and lots and lots of other similar things.  The new file
 misc/memory_info.py has similar problems.  This was all introduced in this
 ticket, so I assume it is related... but maybe there was a followup I am
 unaware of?  Thanks for any feedback.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13211#comment:251>
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