Compatibility with newer Pygments. - #10
Closed
thatch wants to merge 1 commit into
Closed
Conversation
When upstream Pygments dropped py2 support, the compatibility parts were removed; this is a half-vendored copy of the lexer mapping, which still needs them until py2 support is eventually dropped in typecode and/or this gets more fully vendored.
Member
|
Thank you ++ |
Author
|
I'm closing this, I don't think it is necessary after e8655f0 |
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.
When upstream Pygments dropped py2 support, the compatibility parts were
removed; this is a half-vendored copy of the lexer mapping, which still needs
them until py2 support is eventually dropped in typecode and/or this gets more
fully vendored.