#10341: make MIP backend interface more Python-ic
----------------------------------------------+-----------------------------
Reporter: malb | Owner: ncohen
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-4.6.1
Component: linear programming | Keywords: LP, MIP
Author: Martin Albrecht, Nathann Cohen | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
----------------------------------------------+-----------------------------
Comment(by ncohen):
Replying to [comment:24 malb]:
> So what about:
> * If the user wants to use names then (s)he has to provide them at
creation time of variables or constraints.
> * Solvers which don't support them, simply ignore them.
> * In show, if there is a custom name set (queried by backend.col_name()
and backend.row_name()) then it is used for printing
> * When writing lp we do the same?
.....
Sounds logic enough `:-p`
It just exposes I had a stupid idea when I wrote this set_row_name in the
first place. And I guess it's only fitting that I clean my own mess.
Please comment the code from mip.py you need to make your patch run and
pass doctests, and I'll change what is needed there when dealing with Coin
and CPLEX !
Nathann
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10341#comment:25>
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.
