Helloooooooooooo !! Here is a more responsible answer : I just created ticket #15572 to raise exceptions when a function is called which isn't supposed to deal with multiple edges and/or loops. I hope I found them all, but in any case now protecting such functions will just take one line. Aaaaaaaaaaaand of course, if a function isn't supported for non-simple graphs even though it would have a meaning to do so, it will have to be implemented eventually :-)
Buuuuut in the meantime, no more wrong answers :-P http://trac.sagemath.org/ticket/15572 Nathann On Tuesday, December 17, 2013 1:30:27 PM UTC+1, Nathann Cohen wrote: > > > if i understand correctly, Nathann is implying that > > if one works will multigraphs they shouldn't use sage > > for this task. > > Indeed. Or that they should attempt to code what they need, because right > now I wouldn't feel confortable myself computing stuff on multigraphs. > > > agree with this and do so. > > Good luck ! > > Nathann > -- You received this message because you are subscribed to the Google Groups "sage-support" 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-support. For more options, visit https://groups.google.com/groups/opt_out.
