#18032: Broken copy, plot in sandpile
-------------------------------------+-------------------------------------
Reporter: vbraun | Owner:
Type: defect | Status: positive_review
Priority: major | Milestone: sage-6.6
Component: graph theory | Resolution:
Keywords: sd66 | Merged in:
Authors: Peter Wicks | Reviewers: Nathann Cohen
Stringfield, Volker Braun | Work issues:
Report Upstream: N/A | Commit:
Branch: | c500bfa13492c6c51ea52a5b9c0b91fe7b47806a
u/vbraun/ticket/18032 | Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by vbraun):
Replying to [comment:12 ncohen]:
> Looks good. About the graph's `copy` function, you will appreciate that
`G.copy()` does precisely what you expect. Then, if you ask it to do more
it will do... What you ask it to `:-P`
No, `G.copy` does not do what I expect it to do. I've never before seen a
copy method with a dozen arguments. I expect it to make a copy of
``self``, and I expect it to do nothing else.
By the same argument, how about we rename `Matrix.change_ring` to
`Matrix.copy` since a) the changed-ring matrix is still `==` comparable,
and b) you could pass in the same ring to make a copy. But I hope you can
agree that this would be ridiculous.
--
Ticket URL: <http://trac.sagemath.org/ticket/18032#comment:14>
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.
