Networkx 3 compatibility #1447
Merged
Networkx 3 compatibility #1447
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 was
linked to
issues
Jun 7, 2024
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.
I've done with a deeper investigation of upgrading to networkx3. For the downstream repositories listed below I checked any usage of networkx and cross checked any function calls with the full repository diff between 2.0.0 and 3.3 to see if any update might be needed, tested the code in some cases where it wasn't clear if the update would disrupt its implementation and ran the tests for the repository with networkx 3.3 installed.
Investigated repositories:
No issues related to removing the networkx<3 constraint were found in the investigation.
Resolves #1442 and #1445.