#6456: Upgrade cvxopt in sage from 0.9 to 1.1.2
--------------------------------+-------------------------------------------
   Reporter:  was               |       Owner:  mabshoff  
       Type:  defect            |      Status:  needs_work
   Priority:  major             |   Milestone:  sage-4.5.2
  Component:  packages          |    Keywords:            
     Author:  schilly, dimpase  |    Upstream:  N/A       
   Reviewer:                    |      Merged:            
Work_issues:                    |  
--------------------------------+-------------------------------------------

Comment(by pjeremy):

 Replying to [comment:54 dimpase]:
 > Replying to [comment:50 pjeremy]:
 > > 6456-freebsd-spkg-install.patch adds support for FreeBSD (this is a
 port of the patch in #9601).  I have compile-tested this but not yet tried
 to use the resultant module.
 > >
 > > Note that further changes are necessary for cvxopt-1.1.2.p1.spkg to
 work on most 64-bit OSs.
 >
 > could it simply be that some -m64 or whatever flag settings to be added
 to spkg-install?

 No.  The code is wrong/buggy/broken.  The breakage is probably hidden in
 32-bit builds.

 > It can very well be that the standalone cvxopt does not work on that
 fancy 64-bit systems anyway. If this is the case, I am not willing to do
 anything on this at this ticket.

 I do not consider an amd64/x86_64 system to be "fancy".  I suspect that
 anyone wanting to do serious work with Sage will be using a 64-bit system.

 > Last but not least, I would object in strongest possible terms to call a
 blocker an issue that is present in the current cvxopt (0.9) spkg. We must
 upgrade, and then try to improve, and not sit endlessly here...

 There is little point in upgrading to a package that is known to be
 broken.  This particular bug does not appear to be present in cvxopt-0.9
 (at least I can't find the "incompatible pointer type" warnings in either
 my own or boxen builds) so by upgrading, we would be introducing a
 regression into Sage.  I am very concerned at this "release it now, we'll
 make it work later" mentality.  If Sage is going to be a viable
 alternative to the M's, it needs to be trustworthy - complaints of
 "feature X is missing" are easily rectified, claims of "Sage gave me wrong
 answers" can quickly turn into "you can't trust the output from Sage" and
 are far more difficult to refute.

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