#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]:
> The main problem is that if you want to change the current behaviour of
the function (i.e. if you want nonnegative=False to be the default) then
you will have to "make nonnegative mandatory" for a while and raise a
warning when it is not set.
I agree with this, but I don't see the problem. The deprecation warning
from #15521 isn't a problem either...
--
Ticket URL: <http://trac.sagemath.org/ticket/16504#comment:4>
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.
