> My recommended solution/workaround, for the time being, is for affected users to install lxml using 'pip install --no-binary lxml lxml' to force it to be built locally, which will also result in using shared libxml2 instead of static.
I just discovered that using libxml2 2.10.0 results in `etree.fromstring` returning None valid html pages. I would appreciate it if lxml would upgrade its supported libxml2 versions.
> My recommended solution/ workaround, for the time being, is for affected users to install lxml using 'pip install --no-binary lxml lxml' to force it to be built locally, which will also result in using shared libxml2 instead of static.
I just discovered that using libxml2 2.10.0 results in `etree.fromstring` returning None valid html pages. I would appreciate it if lxml would upgrade its supported libxml2 versions.