Dan Schult

If this copy code works for nx-loopback -- I think we should update the copy methods in the base classes to ensure that the neighbor/adjacency order is maintained when users...

The timing results I was getting are apparently a "feature" of my local testing environment. I would like some help in getting my environment set up better. Running `NETWORKX_TEST_BACKEND=nx-loopback pytest...

I've now found that I can get `nx-loopback` testing feature working while testing the whole library so long as I don't try to use the `--doctest-modules` option. :) Both of...

This change to keep edge order consistent during nx-loopback conversion is ready for review. It should work to make #7398 pass the dispatch tests -- but I haven't tested that...

Thanks for those comments and suggestions @rossbar. I have made the suggested changes. And @eriknw has reviewed the PR with comments/suggestions above. So I think it is ready to merge...

Thanks @eriknw I found the `dispatch_interface.py` module yesterday -- and I agree it should probably be moved. Maybe to `utils/tests`. This might be a case we want to add to...

This is a question about backend conversions -- so not directly related to nx-loopback, but I'm hoping it is causing errors for nx-loopback so I can solve them. :) This...

OK... Thanks for that clarification -- and that correction pointing out that G1 is actually a networkx graph arising by converting the backend graph used by the backend back to...

Thank you @paulbroderson !! This is very helpful to point out. And incredibly generous of you to grant an exclusive relicense. Quite disappointing that the code and comments(!) are so...

This does raise for a negatively weighted **selfloop** edge. If an edge between two distinct nodes has negative weight it will only cause an error to be raised if it...