#14535: Mutability of Graphs
------------------------------------+---------------------------------------
Reporter: SimonKing | Owner: jason, ncohen, rlm
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-5.10
Component: graph theory | Resolution:
Keywords: mutability graph | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Simon King | Merged in:
Dependencies: #14524 | Stopgaps:
------------------------------------+---------------------------------------
Changes (by ncohen):
* cc: jernej (added)
Comment:
Hello !
* Could you show that there is no slowdown in the graph functions because
of that please ?
* Besides, why do you need decorators in the Python classes if you forbid
modifications directly in the backend ?
* You create 4 functions in a class that already has a LOT of them. We
have several functions that work like that already :
{{{
sage: g.mutable()
Tells you if it is mutable
sage: g.mutable(True)
Sets it to be mutable
}}}
* There is a lot of things that graphs store and which are not vertices,
nor edges. For example the vertices' layout, or its name... You can see
the list of these awful things in `GenericGraph.__eq__`. If you just want
to take edges and vertices in consideration could you say it explicitely
in the documentation of the `*_mutable` methods ?
And.. Well.. Could you add me in Cc when you write things like that ?
Nathann
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14535#comment:2>
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
