Closed thibaudcolas closed 6 years ago
This change had a similar issue to #88. It seems different lxml (or libxml2?) versions produce a different output. For a specific sequence of unescaped HTML characters (<p>Invalid < " > &</p>
, or potentially something as simple as <p>Invalid < 3</p>
).
Trying to isolate this, it the difference seems to be between v3.7.1 and below, vs v3.7.2 and up:
I'll try to repro this further and report it on lxml or libxml.
Fixes #75.
The only user-facing changes are:
This PR also updates the tox environments, as described in #75.