[sage-devel] Re: networkx BipartiteGraph

2017-12-15 Thread Dima Pasechnik
As expected, it's a networkx bug, that I am proposing them to fix in https://github.com/networkx/networkx/pull/2800 On Thursday, December 14, 2017 at 9:57:25 AM UTC, Antonio Rojas wrote: > > Hi all, > In Arch we have upgraded networkx to version 2. This comes with major > API changes that affe

[sage-devel] Re: networkx BipartiteGraph

2017-12-14 Thread Dima Pasechnik
On Thursday, December 14, 2017 at 11:29:33 AM UTC, Antonio Rojas wrote: > > El Thu, 14 Dec 2017 11:09:17 +, Vincent Delecroix escribió: > > > What about > > > > sage: A = networkx.complete_bipartite_graph(2r, 3r) > > That works correctly: > > sage: A=networkx.complete_bipartite_graph(2r,

[sage-devel] Re: networkx BipartiteGraph

2017-12-14 Thread Antonio Rojas
El Thu, 14 Dec 2017 11:09:17 +, Vincent Delecroix escribió: > What about > > sage: A = networkx.complete_bipartite_graph(2r, 3r) That works correctly: sage: A=networkx.complete_bipartite_graph(2r,3r) sage: list(A.edges()) [(0, 2), (0, 3), (0, 4), (1, 2), (1, 3), (1, 4)] -- You received th

[sage-devel] Re: networkx BipartiteGraph

2017-12-14 Thread Dima Pasechnik
On Thursday, December 14, 2017 at 9:57:25 AM UTC, Antonio Rojas wrote: > > Hi all, > In Arch we have upgraded networkx to version 2. This comes with major > API changes that affect Sage's interface, and I'm currently trying to fix > these issues. I'm struggling with a particular issue with bi