Bring sphinx updates from development to master#331
Merged
Conversation
Bump sphinx to 4.5.0
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
__init__.pyThe sphinx updates in #325 were merged to development but it would be nice to have them on master as well (see docs build failure in #326). Merging development to master is not a good solution at this point because it has other changes we're not ready to merge to master yet, so this branch reflects an earlier state of the development branch with only the sphinx changes.
Note: #325 was merged (not squash-and-merged), so we should probably do the same here to have the same commit history on master as we have on development.