#16504: Fix the confusion in MILP.new_variable()
--------------------------------------+------------------------
Reporter: jdemeyer | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-6.3
Component: linear programming | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
--------------------------------------+------------------------
Comment (by jdemeyer):
Replying to [comment:2 ncohen]:
> That was the point of #15521.
I don't think that #15521 made things more clear...
How about this:
we require at most one of `integer`, `binary`, `real` to be given, with
`real` the default if none is given.
`nonnegative` is a boolean determining whether or not the variable is
assumed to be nonnegative. In the function, we have `nonnegative=None` by
default which is currently interpreted as `nonnegative=True` but with the
warning from #15521.
I think this proposal is backwards- and forwards-compatible (unlike
#15521, which is backwards- but not forwards-compatible).
--
Ticket URL: <http://trac.sagemath.org/ticket/16504#comment:3>
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 http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
