-
Notifications
You must be signed in to change notification settings - Fork 193
Add guide on using retworkx for networkx users #252
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This commit adds a new documentation guide for current networkx users on how to start using retworkx or how to migrate existing networkx code. It provides a high level explanation of the differences in behavior between the 2 libraries and how you can you can switch between them. Fixes Qiskit#248
Pull Request Test Coverage Report for Build 603654702
💛 - Coveralls |
I think there is still some more we can add here, but this is a decent starting point we can always expand the guide over time. But if people think there are obvious gaps we can add to this before merging. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good on the whole. Few small comments.
Co-authored-by: Kevin Krsulich <kevin@krsulich.net>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pedantic copy editing, as is tradition
docs/source/networkx.rst
Outdated
While retworkx being written in Rust puts more constraints on how | ||
you interact with graph object. With retworkx you can still attach any Python |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sentence feels like a fragment.
Co-authored-by: Corey Mendell <corey.mendell@gmail.com>
This commit adds a new documentation guide for current networkx users on
how to start using retworkx or how to migrate existing networkx code. It
provides a high level explanation of the differences in behavior between
the 2 libraries and how you can you can switch between them.
Fixes #248
TODO: