Skip to content
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

Merged

Conversation

mtreinish
Copy link
Member

@mtreinish mtreinish commented Nov 17, 2022

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

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
@mtreinish mtreinish added the Changelog: API Change Include in the "Changed" section of the changelog label Nov 17, 2022
@mtreinish mtreinish added this to the 0.23.0 milestone Nov 17, 2022
@qiskit-bot
Copy link
Collaborator

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:

@coveralls
Copy link

coveralls commented Nov 17, 2022

Pull Request Test Coverage Report for Build 3499678724

  • 32 of 32 (100.0%) changed or added relevant lines in 21 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 84.583%

Totals Coverage Status
Change from base Build 3499561003: 0.0%
Covered Lines: 62524
Relevant Lines: 73920

💛 - Coveralls

Copy link
Member

@jakelishman jakelishman left a 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.

Comment on lines -513 to +517
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
Copy link
Member

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.

Copy link
Member Author

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. :)

qiskit/utils/optionals.py Outdated Show resolved Hide resolved
Co-authored-by: Jake Lishman <jake@binhbar.com>
@mtreinish
Copy link
Member Author

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.

jakelishman
jakelishman previously approved these changes Nov 18, 2022
Copy link
Member

@jakelishman jakelishman left a 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.

@IvanIsCoding
Copy link
Contributor

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.

Let's merge Matthew's PR as it is ready, they are the same diff

@mergify mergify bot merged commit b9def99 into Qiskit:main Nov 18, 2022
@mtreinish mtreinish deleted the rustworkx-not-retworkx-one-day-I-will-remember branch November 18, 2022 21:39
Cryoris pushed a commit to Cryoris/qiskit-terra that referenced this pull request Jan 12, 2023
* 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>
ElePT pushed a commit to ElePT/qiskit that referenced this pull request Jun 27, 2023
* 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>
ElePT pushed a commit to ElePT/qiskit-algorithms-test that referenced this pull request Jul 17, 2023
* 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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Changelog: API Change Include in the "Changed" section of the changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants