Repository navigation
fix: require the mistune release that parses nested emphasis - #21
Merged
Merged
Conversation
`**bold and *italic***` parses as literal text on mistune 3.0 through 3.2, and as nested tokens from 3.3 on. The floor allowed both, so the same document could come out with visible asterisks or with real emphasis depending on which release the resolver happened to pick, and the suite passed or failed to match. 3.3.0 is from June and still supports every Python version this project does, so there is no reason to keep accepting the older behavior.
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
1 participant
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.
**bold and *italic***parses as literal text on mistune 3.0 through 3.2, and as nested tokens from 3.3 on. The floor allowed both, so the same document could come out with visible asterisks or with real emphasis depending on which release the resolver happened to pick, and the suite passed or failed to match.3.3.0 is from June and still supports every Python version this project does, so there is no reason to keep accepting the older behavior.