#20664: MixedIntegerLinearProgram/MIPVariable API cleanup
---------------------------+----------------------------
Reporter: mkoeppe | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: sage-7.3
Component: numerical | Keywords: lp
Merged in: | Authors:
Reviewers: | Report Upstream: N/A
Work issues: | Branch:
Commit: | Dependencies: #20462
Stopgaps: |
---------------------------+----------------------------
Follow-up on #20462:
- Why does a `MIPVariable` only have `set_max`, but no `get_max`?
- Why does `MixedIntegerLinearProgram.set_max` delegate to a
`MIPVariable` method of the same name, when other
`MixedIntegerLinearProgram` methods such as `set_integer` etc. just do
everything directly, and no corresponding `MIPVariable` methods exist?
- Actually these things should properly be referred to as `lower_bound`
and `upper_bound` rather than `min` and `max`. Some deprecation fun to be
had.
- Why is there no way to query the values of the components of the
`_default_mipvariable`?
--
Ticket URL: <http://trac.sagemath.org/ticket/20664>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
