Doc: Fixed compatibility issue with empy #1286
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
FlorianReimold
pushed a commit
that referenced
this pull request
Jan 19, 2024
FlorianReimold
pushed a commit
that referenced
this pull request
Jan 19, 2024
FlorianReimold
pushed a commit
that referenced
this pull request
Jan 23, 2024
FlorianReimold
pushed a commit
that referenced
this pull request
Jan 23, 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.
At the moment it seems to be the case that the recently released version 4.0.0 (end of nov) of python package empy is not compatible with our sphinx documentation build. As short-term fix the package version can be pinned to the previous version 3.3.4 so that the documentation build on the master branch works again.
Cherry pick to