Pin lxml in constraints #1154
Merged
Pin lxml in constraints #1154
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
The recent lxml 5.2.0 release is raising an exception about a packaging change that moved a submodule into a different location during the docs build. We don't actually directly use lxml in rustworkx (or the docs), but it gets pulled in via a dependency of jupyter-sphinx (it's deeper in the dependency tree than jupyter-sphinx's immediate dependencies). To workaround this until things are updated to take this into account this commit pins the lxml version in the constraints.txt file so we don't pull in the latest release.
Pull Request Test Coverage Report for Build 8512519057Details
💛 - Coveralls |
IvanIsCoding
approved these changes
Apr 1, 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.
The recent lxml 5.2.0 release is raising an exception about a packaging change that moved a submodule into a different location during the docs build. We don't actually directly use lxml in rustworkx (or the docs), but it gets pulled in via a dependency of jupyter-sphinx (it's deeper in the dependency tree than jupyter-sphinx's immediate dependencies). To workaround this until things are updated to take this into account this commit pins the lxml version in the constraints.txt file so we don't pull in the latest release.