Repository navigation
Conversation
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
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.
_encode_amps_and_anglesruns four regexes on each span of text. This change skips each regex when the text does not contain its character (&,<or>). The naked>regex now starts with the>, so the regex engine does not try each position in the text. The output does not change.Time of
markdown2.markdown(), median of 20 interleaved rounds. Before and After are CPython 3.14:README.mdof this repoCHANGES.mdof this reposyntax.mdREADME.mdtablesextra)perf/recipes.pprint)test/tm-casesText where every span has
&,<and>is not slower. On PyPy 3.11, the results were in the noise. Import time did not change. I used a Mann-Whitney test (Apple M5). I did not measure other architectures.Checks:
make testoneandmake testredospass on CPython 3.10, 3.14 and PyPy 3.11.