Pin Pygments due to indentation changes in 2.19 #3446
Merged
+2
−2
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
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.
Another day, another wrench thrown into our functional test output because of what appear to be spurious indentation changes introduced by Pygments 2.19. (Pygments 2.19.1 does not appear to address this problem.)
Rather than update our functional test output with what appear to be sub-optimal indentation changes, for now I would rather pin Pygments (yet again) until we decide how to sort things out in a more long-term manner.
The failing test in this PR is related to Typogrify 2.1 and can be ignored, as it will be fixed when #3438 is merged.