#20657: More fixes for copying a MIP and the MIPVariables created by
new_variable
-------------------------+----------------------------
Reporter: mkoeppe | Owner:
Type: defect | 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:
Stopgaps: |
-------------------------+----------------------------
This is a follow-up on #20461.
* a new `MixedIntegerLinearProgram.copy` method that takes a `names`
keyword argument, enabling this operation:
{{{
sage: p.<x,y> = MixedIntegerLinearProgram()
sage: q.<newx,newy> = p.copy()
}}}
and the less magical syntax
{{{
sage: q, newx, newy = p.copy([x, y])
}}}
* if `MixedIntegerLinearProgram.new_variable` has been called, it should
set a flag and then if `__copy__` (or `__deepcopy__`) are called, it
should display a warning (deprecation??) and refer the user to the new
`copy` method.
--
Ticket URL: <http://trac.sagemath.org/ticket/20657>
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.
