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
Rename retworkx to rustworkx #644
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit renames the retworkx project to rustworkx. The maintainers of NetworkX requested that we change the name of the library because they viewed networkx as being too similar to retworkx. Out of respect for this request and the NetworkX library which inspired retworkx we are renaming the library to rustworkx. Rustworkx is a similar name to retworkx and enables us to keep using the rx abbreviation for imports which is commonly used. This commit, migrates all the internal usage and names from retworkx to rustworkx. This includes the retworkx-core crate which has similarly been renamed to rustworkx-core. However, for backwards compatibility and to ease the migration of our existing user base the retworkx package is still included in rustworkx. An import redirect is added so that import retworkx.foo will return return rustworkx.foo. Additionally, the README and documentation are updated to mention the rename. The migration plan this commit takes is that for the pending 0.12.0 release we'll migrate to rustworkx for everything but keep the backwards compatibility shim in place with no warning. In the 0.13.0 release we'll emit a DeprecationWarning (or a FutureWarning) that the name is deprecated (this waits a release to ensure there is upgrade path where > 1 version works without raising a warning to ease migration). We can then remove the deprecated retworkx name as part of the 1.0.0 release. During the transition period we'll continue to publish releases to both the rustworkx and retworkx names through at least 0.14.0 (but with the option to keep publishing both until 1.0.0) so that users will see the deprecation warnings when importing retworkx. Closes Qiskit#641
mtreinish
force-pushed
the
renase-retworkx
branch
from
July 25, 2022 15:00
704dd50
to
7d5f3f6
Compare
This commit splits out the retworkx component from the rustworkx package. This makes the new rustworkx package solely contain the rustworkx piece and the retworkx piece becomes an independent package that depends on rustworkx (and will internally redirect everything to rustworkx). Co-authored-by: Ivan Carvalho <ivancarv@student.ubc.ca>
It turns out that adding a dependency is not going to work prior to the rustworkx package being released because pip won't be able to resolve the rustworkx dependency. This commit reverts this structure for the time being. Closer to the 0.12.0 release we can revisit this and plan to do this structure (maybe by releasing rustworkx first, making this change and then releasing retworkx with the dependency). This reverts commit 2ae3ffd.
Pull Request Test Coverage Report for Build 2750474154
💛 - Coveralls |
I think if we install |
IvanIsCoding
approved these changes
Jul 27, 2022
georgios-ts
approved these changes
Jul 27, 2022
Co-authored-by: georgios-ts <45130028+georgios-ts@users.noreply.github.com>
sgtm |
mtreinish
added a commit
to mtreinish/qiskit
that referenced
this pull request
Aug 5, 2022
The retworkx project was recently renamed rustworkx (see Qiskit/rustworkx#644) however the documentation is still being published to the retworkx url. The project will soon start uploading builds to qiskit.org/documentation/rustworkx in order to prepare for that this commit adds the path to the exlude list so syncs of the main qiskit documentation do not accidently delete the rustworkx documentation.
mtreinish
added a commit
to mtreinish/retworkx
that referenced
this pull request
Aug 5, 2022
In Qiskit#644 we added the build/install of the rust coreutils package to the retworkx backwards compat CI job to have a consistent cross platform way to set environment variables between different OSes. However, this adds significant time to the CI job while we build this package. This commit reconfigures the job to leverage github actions native environment variable handling and drops the coreutils usage. This should speed up the backwards compat jobs since we no longer are compiling coreutils from source.
mergify bot
pushed a commit
to Qiskit/qiskit-metapackage
that referenced
this pull request
Aug 5, 2022
The retworkx project was recently renamed rustworkx (see Qiskit/rustworkx#644) however the documentation is still being published to the retworkx url. The project will soon start uploading builds to qiskit.org/documentation/rustworkx in order to prepare for that this commit adds the path to the exlude list so syncs of the main qiskit documentation do not accidently delete the rustworkx documentation.
mergify bot
pushed a commit
that referenced
this pull request
Aug 5, 2022
In #644 we added the build/install of the rust coreutils package to the retworkx backwards compat CI job to have a consistent cross platform way to set environment variables between different OSes. However, this adds significant time to the CI job while we build this package. This commit reconfigures the job to leverage github actions native environment variable handling and drops the coreutils usage. This should speed up the backwards compat jobs since we no longer are compiling coreutils from source. Co-authored-by: Ivan Carvalho <8753214+IvanIsCoding@users.noreply.github.com>
1 task
mtreinish
added a commit
to mtreinish/retworkx
that referenced
this pull request
Jan 8, 2024
The rustworkx mpl_draw() function was originally adapted from networkx's matplotlib based drawer and heavily modified to work with rustworkx and also conform more to rustworkx's interface style. Attribution to the original source and the license terms of the original networkx code are present in a comment at a top of the module. This port was originally done when rustworkx was still called retworkx. As part of the name migration in Qiskit#644 an overzealous find/replace broke the URL to the permalink to the original networkx source code that the mpl_draw() function was based on. This commit corrects this oversight so that the link correctly resolves to the proper url.
mergify bot
pushed a commit
that referenced
this pull request
Jan 8, 2024
The rustworkx mpl_draw() function was originally adapted from networkx's matplotlib based drawer and heavily modified to work with rustworkx and also conform more to rustworkx's interface style. Attribution to the original source and the license terms of the original networkx code are present in a comment at a top of the module. This port was originally done when rustworkx was still called retworkx. As part of the name migration in #644 an overzealous find/replace broke the URL to the permalink to the original networkx source code that the mpl_draw() function was based on. This commit corrects this oversight so that the link correctly resolves to the proper url. Co-authored-by: Ivan Carvalho <8753214+IvanIsCoding@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit renames the retworkx project to rustworkx. The maintainers of
NetworkX requested that we change the name of the library because they
viewed networkx as being too similar to retworkx. Out of respect for
this request and the NetworkX library which inspired retworkx we are
renaming the library to rustworkx. Rustworkx is a similar name to
retworkx and enables us to keep using the rx abbreviation for imports
which is commonly used.
This commit, migrates all the internal usage and names from retworkx to
rustworkx. This includes the retworkx-core crate which has similarly been
renamed to rustworkx-core. However, for backwards compatibility and to
ease the migration of our existing user base the retworkx package is
still included in rustworkx. An import redirect is added so that
import retworkx.foo will return return rustworkx.foo. Additionally, the
README and documentation are updated to mention the rename.
The migration plan this commit takes is that for the pending 0.12.0
release we'll migrate to rustworkx for everything but keep the backwards
compatibility shim in place with no warning. In the 0.13.0 release we'll
emit a DeprecationWarning (or a FutureWarning) that the name is
deprecated (this waits a release to ensure there is upgrade path where
more than 1 version works without raising a warning to ease migration). We can
then remove the deprecated retworkx name as part of the 1.0.0 release.
During the transition period we'll continue to publish releases to both
the rustworkx and retworkx names through at least 0.14.0 (but with the option
to keep publishing both until 1.0.0) so that users will see the deprecation
warnings when importing retworkx.
Closes #641