#13112: inconsistency calling functions for weighted graphs
----------------------------+-----------------------------------------------
Reporter: dkrenn | Owner: jason, ncohen, rlm
Type: enhancement | Status: new
Priority: major | Milestone: sage-5.1
Component: graph theory | Keywords: weight graph
Work issues: | Report Upstream: N/A
Reviewers: | Authors:
Merged in: | Dependencies:
Stopgaps: |
----------------------------+-----------------------------------------------
Consider the following example:
{{{
G = Graph([(1,2,0.1), (2,3,0.5), (1,3,0.3), (1,4,0.1)]) # whatever
G.min_spanning_tree(weight_function=lambda e:e[2])
w, L = T.longest_path(use_edge_labels=True)
}}}
In the last two lines, the functions are called differently, which is
annoying, since one always has to look up the doc, to find out, which one
is the correct.
Since both ways of calling are good ({{{use_edge_labels}}} simple and
easy, {{{weight_function}}} more flexible), either should be possible for
each function.
I would guess, that there are more functions, which are affected...
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13112>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
