Repository navigation
Release v2.1.0 - #24
Merged
Merged
Conversation
This resolves some IDE warnings: * An unused `method` variable * A type annotation consideration
In the worst case, peak memory use was more than 5x the input payload size.
Documentation build overview
|
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.
Fixed
Close tags more correctly, even if the end tag has trailing text.
For example,
</tag bonus>now closes<tag>correctly.The trailing content is not available to parsers.
Fix quadratic CPU usage in
SGMLParser.feed().This can occur when a large document with an unfinished token
(like
<a href="...) is fed into the parser in very small increments.The new implementation doesn't significantly change peak memory usage.
Changed
Improve the closing tag search behavior of
SGMLParser.finish_endtag().Previously, the method always searched the entire tag stack
to close the innermost tag, which had a higher search cost.
The tag stack is now searched in reverse order
and breaks on the first matching tag.