The following commit authors need to sign the Contributor License Agreement:

• thomasbenardo96@gmail.com

Click the button to sign:

Every change to Python requires a NEWS entry.

Please, add it using the blurb_it Web app or the blurb command-line tool.

I'm porting the html.parser along with the ParserBase class to Lua.
I would love to submit pull request on every performance improvement opportunity that I find.

A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated.

Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

Every change to Python requires a NEWS entry.

Please, add it using the blurb_it Web app or the blurb command-line tool.

There is a lot of wasteful CPU code in this fashion (seen multiple times) :-

if ")" in rawdata[j:]:
    j = rawdata.find(")", j) + 1

search performed in string twice, even if we could just do it once.
Consider the strings immutable, then only every slice a new string is created on the fly.
moreover, the slicing done at rawdata[j:], is bound to be quite expensive depending on the size of the string.
We could eliminate slicing altogether and only have one find operation in this style.

RPAREN_pos = rawdata.find(")", j)
if find_RPAREN != -1:
    j = RPAREN_pos + 1

I'm new to Open Source Code Contributions. Would love to learn from other's coding style & know other's point of view.

I'm porting the html.parser along with the ParserBase class to Lua. I would love to submit pull request on every performance improvement opportunity that I find.

You should create an issue to discuss your changes, and possibly several PRs linked to the issue for the optimizations you find. The optimizations should also be confirmed by benchmarks whenever possible. I should have around some code I used to test/benchmark that I might publish if you think it might be useful.

While you are at it, it would also be useful to improve testing (this will be especially useful for you if you are validating your parser against the HTMLParser test suite) and possibly helpreview/fix related HTMLParser issues.

I have created an issue #92088
Also, I haven't done much automated testing.
Not sure how to make the benchmarks. Do I have to prepare a few html files and check it's parsing order?
Any resources would be really helpful.

The following commit authors need to sign the Contributor License Agreement:

• thomasbenardo96@gmail.com