MAINT: pin pydata sphinx theme and update regression tests #862
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
agoose77
force-pushed
the
agoose77/fix-pin-pydata-sphinx-theme
branch
from
834ac48
to
933bfd8
Compare
agoose77
force-pushed
the
agoose77/fix-pin-pydata-sphinx-theme
branch
from
d3f68a5
to
ef36307
Compare
|
@choldgraf I'm pinging you to let you know that I'm removing most usages of We still use |
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.
Our upstream theme has moved to
sphinx>=6.1. Given our limited maintenance resources, we should mirror this to avoid testing two sets of pydata-sphinx-theme versions.myst-parseralso introduces changes to the AST that add to our maintenance burden. Rather than splitting our regression tests to handle a matrix of sphinx and parser versions, I'm going to drop myst-parser usage except for in the smallest of places.