-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Switch from retworkx to rustworkx package #9162
Switch from retworkx to rustworkx package #9162
Conversation
In the retworkx/rustworkx 0.12.0 release the package was renamed from retworkx to rustworkx which was done at the request of the networkx maintainers [1]. While the retworkx name continues to work for backwards compatibility, it is best to move off of the legacy name and start using the new name sooner rather than later. This commit updates all the retworkx usage to the new rustworkx and updates our requirements list to directly depend on rustworkx. [1] https://qiskit.org/documentation/rustworkx/release_notes.html#prelude
Thank you for opening a new pull request. Before your PR can be merged it will first need to pass continuous integration tests and be reviewed. Sometimes the review process can be slow, so please be patient. While you're waiting, please feel free to review other open PRs. While only a subset of people are authorized to approve pull requests for merging, everyone is encouraged to review open pull requests. Doing reviews helps reduce the burden on the core team and helps make the project's code better for everyone. One or more of the the following people are requested to review this:
|
Pull Request Test Coverage Report for Build 3499678724
💛 - Coveralls |
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.
Ivan (@IvanIsCoding) has old PR #8340 that did this too, but that never merged at the time because it was quite a bit before the rename actually happened. I don't know what the two of you want to do about the two PRs.
vf2_call_limit = int(5e4) # Set call limit to ~100ms with retworkx 0.10.2 | ||
vf2_call_limit = int(5e4) # Set call limit to ~100ms with rustworkx 0.10.2 | ||
elif optimization_level == 2: | ||
vf2_call_limit = int(5e6) # Set call limit to ~10 sec with retworkx 0.10.2 | ||
vf2_call_limit = int(5e6) # Set call limit to ~10 sec with rustworkx 0.10.2 | ||
elif optimization_level == 3: | ||
vf2_call_limit = int(3e7) # Set call limit to ~60 sec with retworkx 0.10.2 | ||
vf2_call_limit = int(3e7) # Set call limit to ~60 sec with rustworkx 0.10.2 |
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.
It hardly matters, but rustworkx 0.10.2
never existed.
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.
Heh, you can tell I just ran sed on the repo. :)
releasenotes/notes/rustworkx-not-retworkx-b7c4da600df58701.yaml
Outdated
Show resolved
Hide resolved
Co-authored-by: Jake Lishman <jake@binhbar.com>
As for this PR vs #8340 I think we probably should just move forward with this one. I had forgotten that @IvanIsCoding had tested this a few months ago, if I had seen that PR I would have just pushed to that branch instead of opening a new PR. But assuming @IvanIsCoding doesn't mind since this version is working and up to date already I think it would better to just merge this and get us migrated to the new name sooner rather than later. |
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.
I'm happy to move ahead with merging this. I'll hold off tagging automerge til Ivan's had a chance to respond.
Let's merge Matthew's PR as it is ready, they are the same diff |
* Switch from retworkx to rustworkx package In the retworkx/rustworkx 0.12.0 release the package was renamed from retworkx to rustworkx which was done at the request of the networkx maintainers [1]. While the retworkx name continues to work for backwards compatibility, it is best to move off of the legacy name and start using the new name sooner rather than later. This commit updates all the retworkx usage to the new rustworkx and updates our requirements list to directly depend on rustworkx. [1] https://qiskit.org/documentation/rustworkx/release_notes.html#prelude * Fix release note path * Update releasenotes/notes/rustworkx-not-retworkx-b7c4da600df58701.yaml Co-authored-by: Jake Lishman <jake@binhbar.com> Co-authored-by: Jake Lishman <jake@binhbar.com> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
* Switch from retworkx to rustworkx package In the retworkx/rustworkx 0.12.0 release the package was renamed from retworkx to rustworkx which was done at the request of the networkx maintainers [1]. While the retworkx name continues to work for backwards compatibility, it is best to move off of the legacy name and start using the new name sooner rather than later. This commit updates all the retworkx usage to the new rustworkx and updates our requirements list to directly depend on rustworkx. [1] https://qiskit.org/documentation/rustworkx/release_notes.html#prelude * Fix release note path * Update releasenotes/notes/rustworkx-not-retworkx-b7c4da600df58701.yaml Co-authored-by: Jake Lishman <jake@binhbar.com> Co-authored-by: Jake Lishman <jake@binhbar.com> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
* Switch from retworkx to rustworkx package In the retworkx/rustworkx 0.12.0 release the package was renamed from retworkx to rustworkx which was done at the request of the networkx maintainers [1]. While the retworkx name continues to work for backwards compatibility, it is best to move off of the legacy name and start using the new name sooner rather than later. This commit updates all the retworkx usage to the new rustworkx and updates our requirements list to directly depend on rustworkx. [1] https://qiskit.org/documentation/rustworkx/release_notes.html#prelude * Fix release note path * Update releasenotes/notes/rustworkx-not-retworkx-b7c4da600df58701.yaml Co-authored-by: Jake Lishman <jake@binhbar.com> Co-authored-by: Jake Lishman <jake@binhbar.com> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Summary
In the retworkx/rustworkx 0.12.0 release the package was renamed from retworkx to rustworkx which was done at the request of the networkx maintainers [1]. While the retworkx name continues to work for backwards compatibility, it is best to move off of the legacy name and start using the new name sooner rather than later. This commit updates all the retworkx usage to the new rustworkx and updates our requirements list to directly depend on rustworkx.
Details and comments
Closes #8340 (obsolete)
[1] https://qiskit.org/documentation/rustworkx/release_notes.html#prelude