Hello ! > I think that'd be the purpose of the "multiedges=False/True" parameter > that Nathann suggests. > > I could be mistaken, but don't we have such parameter already?
Yesyes, it can already be done by adding this parameter explicitly. My proposal was only to display a warning when a user does *not* specify it *and* the graph is a multigraph. The message would ask him to be expicit in the future, in order to avoid unexpected behaviour. > And since explicit is better than implicit, I'd think it is reasonable > to ask the user to be explicit about graphs or multigraphs. Well.... I would not want to make Graph() invalid by requiring every call to specific explicitly Graph(multiedges=False,loops=False), so I attempted to make it "only a bit more mandatory" by leading users of Graph(list_of_edges_with_repetitions) to add the flag multiedges=True. Do you think that the current situation (latest release) is correct ? Or do you think that we should, instead, make the multiedges/loops parameters mandatory when using the syntax Graph(list_of_edges_with_repetitions) ? If I make no mistake, what you think of this branch is that it is too tame, i.e. that it does not force people to be explicit, and also that because the user was not explicit we are under no obligation to do what he thought very hard but never told us. Cheers, Nathann -- You received this message because you are subscribed to the Google Groups "sage-devel" 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-devel. For more options, visit https://groups.google.com/d/optout.
