You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to have drop-in compatibility with networkx, we could make the default dialect to be nx, such that graph.nx.{method} == graph.{method}. Duck test with nx digraph.
The text was updated successfully, but these errors were encountered:
G now has all the networkx-flavored bells and whistles as your graph var above:
G.add_edge(1, 2)
len(G)
I've hesitated to add any API dialect at the "top level" like you illustrate above because it imposes some restrictions on how the user can use the package: (Why require a networkx install?) Does the graph = grand.Graph(...).nx solution solve this need?
In order to have drop-in compatibility with networkx, we could make the default dialect to be nx, such that
graph.nx.{method} == graph.{method}
. Duck test with nx digraph.The text was updated successfully, but these errors were encountered: