#18028: Remove GraphBundle
-------------------------------------+-------------------------------------
Reporter: vbraun | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: sage-6.6
Component: graph theory | Resolution:
Keywords: | Merged in:
Authors: Volker Braun | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/vbraun/remove_graphbundle | bfb444341d3b3a3f3a546338bc61f79085b9abf1
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by ncohen):
Wow. Glad to see that it is actually possible to remove code from Sage. I
always thought that it was 'politically impossible' to remove anything
from this software, but fortunately I seem to be wrong.
What would you think of removing `BipartiteGraph` while we are at it ?
This class' design is awful:
{{{
sage: g=BipartiteGraph()
sage: l=[(0,1),(3,2),(1,2),(0,3)]
sage: for e in l:
....: g.add_edge(e)
RuntimeError: Edge vertices must lie in different partitions.
}}}
but
{{{
sage: g = Graph()
sage: g.add_edges(l)
sage: g.is_bipartite()
True
}}}
Also, I just noticed that one can very easily build a non-bipartite
`BipartiteGraph`::
{{{
sage: g = BipartiteGraph()
sage: g.add_edges(graphs.CompleteGraph(30).edges())
sage: g.is_bipartite()
False
}}}
Please. Can you help me get rid of that class? I'll write the ticket if
you agree.
Nathann
--
Ticket URL: <http://trac.sagemath.org/ticket/18028#comment:3>
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.
