#8880: CPLEX can now be silenced
-------------------------+--------------------------------------------------
   Reporter:  ncohen     |       Owner:  jason, jkantor
       Type:  defect     |      Status:  needs_review  
   Priority:  major      |   Milestone:  sage-4.4.1    
  Component:  numerical  |    Keywords:                
     Author:             |    Upstream:  N/A           
   Reviewer:             |      Merged:                
Work_issues:             |  
-------------------------+--------------------------------------------------

Comment(by jason):

 (I guess my comment is the same here as it is on #8364.  I still think
 it's a better design, but I haven't used these options in practice, so if
 you think that it is way too annoying, then say so.

 My concerns are:

  1. the options are not related to the actual function, so logically they
 should be separated out from the function options
  1. Anytime we implement a new option for the function (say we make a
 graph-theoretic algorithm to do the same thing), we have to check all
 solvers to see if we are accidentally overriding a keyword option for the
 solver.

 You could also make the options part of the solver keyword, like this:

 edge_cut(solver=("CPLEX", dict(option1=True, option2=False)))

 or

 edge_cut(solver=dict(option1=True, option2=False)) # pick the default
 solver, pass in these options.

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