It's very unlikely that the error you found in test_htmlparser.TestHTMLParserTreeBuilder is related to this patch, for two reasons:
1. The test that fails is testing Python's built-in HTML parser, not lxml. No lxml code should be running.
2. The patch only changes a test (in XMLTreeBuilderSmokeTest), not any code that would be run by the failing test.
In addition, I'm unable to reproduce the issue in my own Python 3.8 environment.
I'd be interested to know:
* Whether the TestHTMLParserTreeBuilder failure is reliably repeatable in your Python 3.8 environment, or whether it's intermittent.
* Whether backing out the patch fixes the TestHTMLParserTreeBuilder failure (at the expense of potentially introducing an lxml test failure)
* Whether installing lxml (and thus libxml2) into an environment that doesn't have the TestHTMLParserTreeBuilder failure, introduces the failure.
It's very unlikely that the error you found in test_htmlparser .TestHTMLParser TreeBuilder is related to this patch, for two reasons:
1. The test that fails is testing Python's built-in HTML parser, not lxml. No lxml code should be running. mokeTest) , not any code that would be run by the failing test.
2. The patch only changes a test (in XMLTreeBuilderS
In addition, I'm unable to reproduce the issue in my own Python 3.8 environment.
I'd be interested to know:
* Whether the TestHTMLParserT reeBuilder failure is reliably repeatable in your Python 3.8 environment, or whether it's intermittent. reeBuilder failure (at the expense of potentially introducing an lxml test failure) reeBuilder failure, introduces the failure.
* Whether backing out the patch fixes the TestHTMLParserT
* Whether installing lxml (and thus libxml2) into an environment that doesn't have the TestHTMLParserT