#18972: twographs and Seidel switching
-------------------------------------+-------------------------------------
Reporter: dimpase | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.9
Component: graph theory | Resolution:
Keywords: | Merged in:
Authors: | Reviewers: Nathann Cohen
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/dimpase/seidelsw | 2fae2fc7b92d306f1336b6786c67318823f812f4
Dependencies: #18960, #18948, | Stopgaps:
#18988, #18991, #18986, #19018, |
#19019 |
-------------------------------------+-------------------------------------
Comment (by dimpase):
Replying to [comment:61 ncohen]:
> You have not fixed the code of `twograph_descendant`, whose
documentation also contains broken links.
done; I also shifted it and the rest of the methods on this ticket to the
**Leftovers** index.
>
> I also find this function to be *very* specific, and I do not think that
it should belong to the Graph class. What about moving it to this
twograph module that you create?
It is not even a function. It is a method of Graph, and it produces a
Graph. There are things in Graph that I also find very specific, yet they
belong there by right.
--
Ticket URL: <http://trac.sagemath.org/ticket/18972#comment:63>
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.
